Northern 171D72
View line Northern
Alerts for train 171D72
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
41%
12/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
40%
36/89 runs under 3 min
RT coverage: 89 full · 0 partial · 0 no data
Typical delay
+3min
Median at arrival, 90 days
30 days: +4 min
P90
+15min
9 in 10 runs arrive with less than this
30 days: +14 min
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
- Fri 4 Sept Max en route +55 min · last fix heading to 40322 +53 min
- Mon 26 Oct Max en route +47 min · last fix heading to Earlestown +37 min
- Thu 6 Aug Max en route +35 min · last fix heading to 29002 +35 min
- Fri 25 Sept Max en route +31 min · last fix heading to 31515 +29 min
- Fri 16 Oct Max en route +29 min · last fix heading to Littleborough +26 min
Distribution · 90 days
89 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 2% · 2
- On time 38% · 34
- 3–10 min 37% · 33
- 10–30 min 19% · 17
- 30+ min 3% · 3
On-time by weekday
- 46% M n=13
- 31% T n=13
- 38% W n=13
- 23% T n=13
- 31% F n=13
- 38% S n=13
- 82% S n=11
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 31 Oct | Earlestown 10:11 | +1 min | +4 min |
| Fri 30 Oct | Earlestown 20:11 | +1 min | +16 min |
| Thu 29 Oct | Earlestown 20:13 | +2 min | +9 min |
| Wed 28 Oct | Earlestown 20:26 | +16 min | +22 min |
| Tue 27 Oct | Earlestown 20:17 | +6 min | +6 min |
| Mon 26 Oct | Earlestown 20:47 | +37 min | +47 min |
| Sat 24 Oct | Littleborough 20:13 | +3 min | +5 min |
| Fri 23 Oct | Earlestown 20:16 | +5 min | +15 min |
| Thu 22 Oct | Earlestown 20:14 | +4 min | +7 min |
| Wed 21 Oct | Earlestown 20:25 | +14 min | +14 min |
| Tue 20 Oct | Littleborough 20:19 | +9 min | +15 min |
| Mon 19 Oct | Earlestown 20:13 | +1 min | +13 min |
| Sun 18 Oct | Littleborough 16:54 | −1 min | — |
| Sat 17 Oct | Earlestown 20:19 | +7 min | +10 min |
| Fri 16 Oct | Littleborough 19:36 | +26 min | +29 min |
| Thu 15 Oct | Earlestown 20:12 | +2 min | +5 min |
| Wed 14 Oct | Earlestown 20:11 | +1 min | +26 min |
| Tue 13 Oct | Earlestown 20:20 | +9 min | +9 min |
| Mon 12 Oct | Earlestown 20:17 | +7 min | +12 min |
| Sun 11 Oct | Littleborough 17:08 | −1 min | +1 min |
| Sat 10 Oct | Earlestown 20:10 | −1 min | +6 min |
| Fri 9 Oct | Earlestown 20:16 | +6 min | +12 min |
| Thu 8 Oct | Earlestown 20:14 | +4 min | +18 min |
| Wed 7 Oct | Earlestown 20:21 | +11 min | +15 min |
| Tue 6 Oct | Earlestown 20:13 | +2 min | +10 min |
| Mon 5 Oct | Earlestown 20:13 | +3 min | +6 min |
| Sun 4 Oct | 31045 17:07 | −2 min | +2 min |
| Sat 3 Oct | 40322 20:11 | 0 min | +9 min |
| Fri 2 Oct | 40322 20:17 | +7 min | +33 min |
| Thu 1 Oct | 40322 20:16 | +5 min | +11 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.