LDN Router · data

London's railways, in numbers

What the trains actually do, read off the feeds that say where they are: how many run, how often, how late, and how much the feed itself gets wrong. Recomputed every night; nothing here is live.

Rebuilt nightly. Every number on this page is plain JSON under /viz-data/, one file per chart, each carrying its build time and data window; the file behind each chart is linked beneath it.

The pulse

How many trains London runs, ten minutes at a time.

Trains in service on every Tube, Overground, DLR and Elizabeth line, in ten-minute bins across the last two weeks, with a typical weekday, Saturday and Sunday trace per line.Data: pulse.json

Turn up and go

The gap to the next train, and how much bunching costs you.

Median and 85th-percentile gaps between trains per line and hour of day, and the extra waiting that uneven gaps add over a perfectly even service, over the last four weeks.Data: headways.json

The reliability tax

Minutes to budget over the typical run, the timetable's optimism, and the slowest mile.

Per line: how many minutes a passenger must budget above the median run to arrive on time 85 times in 100, where the timetable is more optimistic than the trains, and the slowest stop-to-stop runs, from the planner's observed journey-time model.Data: segments.json

The feed lies

What TfL's arrivals feed actually sends, poll by poll.

Of every arrivals poll the logger makes, the share that repeats the previous response, carries a stale timestamp or fails; the blank platform and direction rates per line; and the logger's recent gaps.Data: feed.json

Busiest stations

Train arrivals per day, by station and line.

Train arrivals per weekday at the 25 busiest stations, stacked by line, with weekend averages, and the stations whose arrival predictions TfL revises the most. Stations are grouped by NaPTAN hub; a train published under two stop codes at one station counts once.Data: stations.json

Disruption calendar

Every hour of every line, coloured by the worst thing TfL said about it.

A calendar of line status per hour per line over the last twelve days, and the number of hours each line spent worse than Good Service.Data: status.json

National Rail punctuality

Lateness by operator, hour, weekday and station on the London corridors.

Mean and 85th-percentile lateness at London stations from Historic Service Performance data, by operator, hour of day, day of week and station.Data: nr.json

Great Britain, by the minute

Mean lateness at every station in the country, from the live actuals feed.

The bus network

London by bus

Every bus route, logged like the trains: where the stops are, how fast the buses move between them, and the corridors where they crawl.

Where the buses crawl

Every bus road in London, coloured by how fast the buses on it actually move.

Eight thousand traffic sensors

The speed of London's buses by hour of day is the congestion curve of its roads, and the slowest and fastest routes are its map.

Traffic's reliability tax

How much more variable a bus is than a train, hour by hour, on the busiest routes, and how fast it actually moves.

Bunching

The gap to the next bus on the busiest routes, and what it costs to wait for one.

The logger

The database behind the page.