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