Northern 162K11
View line Northern
Alerts for train 162K11
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.
It does not run today
Last recorded run: Sunday 4 October +2 min
The mini-map returns when the train runs
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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
Distribution · 90 days
8 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 8
- 3–10 min 0% · 0
- 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
- 100% S n=8
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 4 Oct | 17117 10:35 | +2 min | +3 min |
| Sun 27 Sept | 17117 10:33 | 0 min | +2 min |
| Sun 20 Sept | 17117 12:32 | 0 min | +1 min |
| Sun 13 Sept | 17117 10:32 | −1 min | +1 min |
| Sun 6 Sept | 17117 10:32 | −1 min | +1 min |
| Sun 2 Aug | 17117 10:33 | 0 min | +1 min |
| Sun 26 Jul | 17117 10:32 | −1 min | +1 min |
| Sun 19 Jul | 17117 10:33 | 0 min | +2 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.