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