London Real Time

Greater London departures

London moving. One board, right now.

See live bus, Tube, DLR, Elizabeth line and London Overground departures without turning a simple journey into a map exercise.

See how it worksGet help

London Real Time is an independent Rawdestiny app. It is not affiliated with, sponsored by or endorsed by Transport for London.

The station board, without the station.

Choose a stop or station and scan what matters: line, destination, platform when supplied, and expected departure time. Status and disruption context appear only when TfL provides them.

DLRLewisham1 min
ElizabethAbbey Wood4 min
OvergroundRichmond9 min

Useful when the network is not simple.

London Real Time distinguishes live information, timetabled information and saved information. It never invents a platform, crowding value or service status.

Expected time when available

Live arrivals are ordered by TfL's expected arrival time. Timetabled or cached information is labelled so it cannot look newer than it is.

Status in context

Tube, DLR, Elizabeth line and London Overground status can be opened from the board. Disruption wording stays attributable to the provider.

Rail and bus in one search

Search stations and bus stops across Greater London, then keep one place saved in the free experience.

Real departures on your Home Screen.

Small and medium departure widgets are free. Premium adds the large Home Screen widget, Lock Screen widgets, Live Activity, multiple saved places and every original London scene.

No account. No ads. No tracking.

Location is optional. London Real Time has no analytics or advertising SDK and does not ask for tracking permission. Purchases are handled by Apple through StoreKit.

Development roadmap

Planned: ask about your journey with Claude API

We plan to add question answering about public service notices and disruptions, with the provider source and timestamp linked to each answer. Real departure times will continue to come from the transport provider.

This feature is not available in the current app. No Claude API transit integration is deployed.

Planned architecture: the API key stays on the server. Only the context a user chooses for a question is sent to the model. Data handling will be documented before this feature launches.

Read the planned architecture