Northern 321N59
View line Northern
Alerts for train 321N59
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
56%
14/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
59%
45/76 runs under 3 min
RT coverage: 76 full · 0 partial · 0 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+14min
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
- Mon 27 Jul Max en route +52 min · last fix heading to 30116 +49 min
- Wed 30 Sept Max en route +25 min · last fix heading to 30040 +21 min
- Sat 19 Sept Max en route +22 min · last fix heading to 30040 +21 min
- Sat 12 Sept Max en route +22 min · last fix heading to 30040 +21 min
- Sat 29 Aug Max en route +22 min · last fix heading to Deansgate +21 min
Distribution · 90 days
76 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 3% · 2
- On time 57% · 43
- 3–10 min 20% · 15
- 10–30 min 20% · 15
- 30+ min 1% · 1
On-time by weekday
- 54% M n=13
- 69% T n=13
- 67% W n=12
- 58% T n=12
- 77% F n=13
- 31% S n=13
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 20 Oct | Layton (Lancs) 21:33 | 0 min | +6 min |
| Mon 19 Oct | Poulton-le-Fylde 21:33 | 0 min | +19 min |
| Sat 17 Oct | Layton (Lancs) 21:35 | +2 min | +6 min |
| Fri 16 Oct | Layton (Lancs) 21:45 | +12 min | +13 min |
| Thu 15 Oct | Layton (Lancs) 21:47 | +14 min | +16 min |
| Wed 14 Oct | Poulton-le-Fylde 21:32 | −1 min | +15 min |
| Tue 13 Oct | Layton (Lancs) 21:44 | +11 min | +17 min |
| Mon 12 Oct | Poulton-le-Fylde 21:33 | −1 min | +20 min |
| Sat 10 Oct | Layton (Lancs) 21:39 | +6 min | +10 min |
| Fri 9 Oct | Layton (Lancs) 21:33 | 0 min | +8 min |
| Thu 8 Oct | Poulton-le-Fylde 21:37 | +4 min | +9 min |
| Wed 7 Oct | Layton (Lancs) 21:35 | +2 min | +6 min |
| Tue 6 Oct | Poulton-le-Fylde 21:48 | +14 min | +17 min |
| Mon 5 Oct | Layton (Lancs) 21:32 | −1 min | +4 min |
| Sat 3 Oct | 30040 21:46 | +13 min | +20 min |
| Fri 2 Oct | 30040 21:39 | +6 min | +13 min |
| Thu 1 Oct | 30040 21:35 | +2 min | +8 min |
| Wed 30 Sept | 30040 21:54 | +21 min | +25 min |
| Tue 29 Sept | 30040 21:36 | +3 min | +4 min |
| Mon 28 Sept | 30040 21:33 | −1 min | +3 min |
| Sat 26 Sept | 30040 21:40 | +7 min | +10 min |
| Fri 25 Sept | 30040 21:33 | 0 min | +5 min |
| Thu 24 Sept | 30040 21:32 | −1 min | +4 min |
| Wed 23 Sept | 30040 21:31 | −2 min | +6 min |
| Tue 22 Sept | 30040 21:32 | −1 min | +6 min |
| Mon 21 Sept | 30040 21:32 | −2 min | +4 min |
| Sat 19 Sept | 30040 21:54 | +21 min | +22 min |
| Fri 18 Sept | 30040 21:32 | −1 min | +4 min |
| Thu 17 Sept | 30040 21:36 | +2 min | +19 min |
| Wed 16 Sept | 30040 21:36 | +2 min | +12 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.