Northern 172P11
View line Northern
Alerts for train 172P11
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Northern.
The mini-map returns when the train runs
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this
Last 30 days
Delay at the end of each run, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Sun 27 Sept Max en route +8 min · last fix heading to 17136 +7 min
- Sun 23 Aug Max en route +3 min · last fix heading to 17136 +3 min
Distribution · 90 days
10 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 8
- 3–10 min 20% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 80% S n=10
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 11 Oct | Frizinghall 13:45 | −1 min | — |
| Sun 4 Oct | 17136 13:46 | 0 min | +1 min |
| Sun 27 Sept | 17136 13:52 | +7 min | +8 min |
| Sun 20 Sept | 17136 13:44 | −1 min | +1 min |
| Sun 13 Sept | 17136 13:47 | +2 min | +3 min |
| Sun 6 Sept | 17136 13:46 | +1 min | +2 min |
| Sun 30 Aug | 17136 13:46 | 0 min | +1 min |
| Sun 23 Aug | 17136 13:48 | +3 min | +3 min |
| Sun 16 Aug | 17136 13:44 | −1 min | — |
| Sun 9 Aug | 17136 13:47 | +1 min | +1 min |
Each run is closed into train_runs (country, train number, service day) from the live positions. Final delay = last delay seen. Partial coverage: the feed stopped before the final stop (last value used, hatched in the chart). No data: a run without any valid delay; counts as neither on time nor late. Data collected since 11 July 2026.