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