DelayometerLondon rail, measured

Live measured status

Waterloo & City line status

DelayedTfL: Good Service

About 3 min longer than usual

Score73out of 100
Added to a journey2 min 37send to end, versus normal
Waiting longer byper train, on average
Running slower by20sper section, on average
Sections scored2of 2 on the line
Confidencelowfrom train speeds only

Live — last reading . Two stations, weekday peaks only. Long stretches with no service at all are the timetable, not a failure.

The last 24 hours

Tue 4 Aug 18:40:00 → 18:35:00

no data

Higher is better; the hairline is the threshold below which a line stops counting as running normally. A dashed stretch along the bottom is a period we have no score for, and it says which kind. No service is the small hours, when the line is not running. No data is us: either nothing reached us, or — more often — we had nothing to compare that stretch against, because a line TfL has declared disrupted for long enough loses those hours from what we count as normal. Neither is a delay, and we would rather show the hole than draw a line across it.

By direction

Towards central London

99

Good

Running normally

Away from central London

64

Delayed

About 3 min longer than usual

One direction can be in trouble while the other runs perfectly, which is exactly what a single line-wide status hides. Platform indicators name the destination rather than the direction — we will too, once the measurement service publishes where each direction ends.

Slowest sections right now

Worst first

WaterlooBank64
BankWaterloo99

Sections are scored on their own, so a line can be fine end to end and still have one stretch that is not. Only measured sections appear here.

Every other line

How this is measured →