About London Tube

londontube.org reads Transport for London’s own open data and lays it out as one page per line and one page per station: 11 lines, 272 stations, plus the map, first and last trains, single fares, a journey planner and separate guides to the Night Tube, to Heathrow and to paying by /oyster-and-contactless/. Nothing here is official. TfL neither runs this site nor checks it, and the operator’s own pages remain the authority on anything you are about to rely on.

What this site covers

The subject is the Underground and only the Underground. The Elizabeth line, the Overground, the DLR and the trams share the same map sheet and the same fare rules, and they are named here whenever they touch a Tube station, but they get no pages of their own: they are different railways with different timetables, and pretending otherwise would mean publishing numbers we never fetched. The station count is the full 272, which is 270 NaPTAN identifiers beginning 940GZZLU plus two that do not follow the pattern at all, Battersea Power Station and Nine Elms. That arithmetic matters because it is the reason our total matches the one TfL prints rather than beating it by a station or two.

Every figure, and the request it came from

Pages are compiled, not typed. Each one is assembled from data files captured from a named source, so a correction lands in the file and reappears everywhere that file is read. The inventory:

• The line list is /Line/Mode/tube from the TfL Unified API, which needs no key and no registration.
• Branch order comes from /Line/{id}/Route/Sequence/{direction}, fetched in both directions, which is what lets a Northern line page show Mill Hill East and Battersea on the right arms instead of flattening everything into one list.
• Zones, coordinates, lifts, step-free access and station opening hours come from /StopPoint/{ids}. At an interchange such as Bank or Euston the endpoint answers with the hub record and hides the station in its children array; the generator reads the child, because the hub has no zone of its own to give.
• First and last trains and the minutes from one platform to the next come from /Line/{id}/Timetable/{station}, requested per station, per direction and per day type. Between two adjoining stations we publish the shortest interval TfL prints for that pair; the planner then adds roughly four minutes wherever you change line.
• Single fares are read station by station from TfL’s Single Fare Finder: adult pay as you go, peak and off-peak, plus the cash price of a paper single. Caps and Travelcard prices on the Oyster and contactless page come from the published adult rate card for 2026, and that page carries the date it was read.
• Opening dates, earlier names and annual usage are the 272 rows of Wikipedia’s list of London Underground stations. Usage is entries and exits during 2024, in millions, as that list gives it.
• Places worth naming near a station are drawn from OpenStreetMap and filtered by category and by distance from the entrance.
• The map is a schematic by the Commons contributor Sameboat, under CC BY-SA 4.0, with our band and logo added. TfL’s diagram is a protected design and is not reproduced.
• Photographs are freely licensed Commons files, credited beside the image and again in the legal notice.

Five things this site refuses to publish

1. Live departures. There is no feed behind this site. The board on the front page sets the London clock against the published timetable and reports whether a line is inside its service hours; it cannot know that your train is four minutes down, and it does not pretend to.
2. Disruption as news. Long closures that TfL announces are recorded with their dates. Today’s signal failure is not: tfl.gov.uk and TfL’s own alerts exist for that, and a stale warning is worse than none.
3. Atmosphere. No station here is called hidden, charming or a must-see, and we do not tell you which end of the platform to stand at. That is knowledge from using a line daily for years, which is not what this site has.
4. Numbers nobody publishes. Platform depth, interchange walking times and per-entrance counts are absent from the API and absent here. A gap is honest; a plausible invention is not.
5. Tickets. Nothing is sold on this site and nothing is resold through it. Oyster, contactless and Travelcards are TfL’s business, and the links go straight to them.

Where TfL and Wikipedia disagree

The two lists were matched on name and on distance, and five rows had to be settled by hand rather than by code. There are two stations called Hammersmith, two called Edgware Road and two called Paddington, each pair on different lines and each pair indistinguishable by name alone. Bank and Monument are the opposite case: one Wikipedia article covers both, but the operator keeps them as separate stations. The unresolved consequences are printed where they occur:

• Bank and Monument report one usage figure between them, and so do the two Paddingtons, because the counts are collected for the joined site. Each page gives the shared number and says whose it is instead of halving it.
• Some timetable responses arrive with a single day type on them and nothing else. Where that happened the missing days were rebuilt from the trains that reach the station from one stop further up the line, which is the same service observed earlier. It holds up, but it is a reconstruction and is labelled as one.
• Amersham and West Ruislip show weekday times only. Trains do run there at weekends, but TfL’s timetable data for these two termini came back with midweek schedules alone, and the reconstruction could not supply the rest. Those two pages say so instead of guessing.
• Kensington (Olympia) runs seven trains on a weekday and that is the whole service. A figure that small normally means depot movements rather than a timetable, and the generator used to discard it; here it is the only weekday service TfL publishes, so it is kept and labelled with the count instead of being thrown away.
• There is no zone 8 row in the fares table. TfL’s own fare finder publishes combinations up to zone 7 and then jumps to zone 9, so that line is simply absent rather than interpolated from its neighbours.
• The diagram is not the operator’s. It is an independent drawing of the same railway, checked against the line and station lists on this site; any schematic trails reality by a few weeks.

Telling us we have it wrong

A wrong zone, a missing lift, a station name with the wrong apostrophe: send it. The fix goes into the data file rather than into the sentence you read, so it propagates to the line page, the planner and the fares table in the same build. Use the contact form or write to [email protected]. What we cannot do is anything to do with your journey — lost property, refunds, Oyster balances, penalty fares. Those belong to tfl.gov.uk, and sending them here only loses you time.

Who pays for it

Advertising covers the hosting and the hours. That is the whole arrangement. No advertiser has ever seen a station page before it went up, no money changes hands for a mention or a link, and nothing on this site is an affiliate placement wearing a recommendation’s clothes. If a commercial relationship ever does affect a page, the page will say so. Which cookies the advertising needs, and how to refuse them, is set out in the cookie policy and the privacy policy.

The publisher

David Franco Aguirre publishes this site under the GoRandom imprint, from Bilbao in Spain. The English is British because the readers are in London; the perspective is not local, and that is worth saying plainly. What is on offer is the operator’s published data, cross-checked, dated, and left with its holes visible.

Last updated: October 2026.