Get in touch
Email is the fastest route. A human reads every message.
Common issues
HP·01 Live data isn't updating
Pull to refresh first. If it's still stale, check your connection — RailTracker needs a signal to fetch live status, though maps and saved lines work offline. TfL's feed occasionally goes quiet during engineering works, in which case the app is showing you the last good data it has.
HP·02 The app crashes or freezes
Force-quit and reopen. If it keeps happening, check the App Store or Play Store for an update — most crashes are fixed within a release or two. Still stuck? Email us with your device model and OS version and it'll get looked at.
HP·03 A station or route is missing
RailTracker uses official TfL data, so gaps usually trace back to the source feed. Tell us which station or route and we'll investigate — sometimes it's a naming mismatch we can fix on our end.
HP·04 Notifications aren't arriving
Check notifications are allowed for RailTracker in your device settings, and that you've selected at least one line to follow inside the app. Alerts only fire for lines you've opted into — that's deliberate, so you don't get woken up about a line you never use.
HP·05 I've got an idea for a feature
Send it. RailTracker's roadmap is shaped mostly by what people actually ask for, and a single good suggestion has changed the plan before.
What to include when you write in
Four things get an issue resolved far faster:
- What you did, and what you expected to happen instead
- Your device model and OS version
- The app version, and whether it's iOS, Android or the web app
- A screenshot, if the problem is something you can see
Privacy and support
We may ask for technical details about your device to resolve an issue. That information is used only to help with your problem — never stored beyond the conversation, and never shared. The RailTracker privacy policy covers what the app itself does and doesn't collect.