Northern 321N62
View line Northern
Alerts for train 321N62
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
79%
22/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
70%
62/88 runs under 3 min
RT coverage: 88 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
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
- Sat 5 Sept Max en route +23 min · last fix heading to 30040 +20 min
- Wed 7 Oct Max en route +14 min · last fix heading to Poulton-le-Fylde +14 min
- Mon 17 Aug Max en route +14 min · last fix heading to 30040 +12 min
- Tue 22 Sept Max en route +12 min · last fix heading to 30331 +11 min
- Thu 13 Aug Max en route +12 min · last fix heading to 30040 +10 min
Distribution · 90 days
88 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 18% · 16
- On time 52% · 46
- 3–10 min 24% · 21
- 10–30 min 6% · 5
- 30+ min 0% · 0
On-time by weekday
- 75% M n=12
- 58% T n=12
- 83% W n=12
- 77% T n=13
- 54% F n=13
- 69% S n=13
- 77% S n=13
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 18 Oct | Layton (Lancs) 18:33 | 0 min | +2 min |
| Sat 17 Oct | Poulton-le-Fylde 23:04 | +2 min | +5 min |
| Fri 16 Oct | Poulton-le-Fylde 23:10 | +9 min | +22 min |
| Thu 15 Oct | Poulton-le-Fylde 23:03 | +2 min | +6 min |
| Wed 14 Oct | Poulton-le-Fylde 23:01 | 0 min | +4 min |
| Tue 13 Oct | Poulton-le-Fylde 23:05 | +4 min | +13 min |
| Mon 12 Oct | Poulton-le-Fylde 23:02 | +1 min | +5 min |
| Sun 11 Oct | Layton (Lancs) 18:30 | −2 min | +4 min |
| Sat 10 Oct | Poulton-le-Fylde 23:01 | 0 min | +5 min |
| Fri 9 Oct | Poulton-le-Fylde 23:05 | +4 min | +10 min |
| Thu 8 Oct | Poulton-le-Fylde 23:00 | −1 min | +4 min |
| Wed 7 Oct | Poulton-le-Fylde 23:16 | +14 min | +14 min |
| Tue 6 Oct | Poulton-le-Fylde 23:02 | 0 min | +3 min |
| Mon 5 Oct | Poulton-le-Fylde 23:01 | 0 min | +6 min |
| Sun 4 Oct | 30040 18:30 | −2 min | +1 min |
| Sat 3 Oct | 30040 22:54 | +6 min | +7 min |
| Fri 2 Oct | 30040 23:01 | 0 min | +4 min |
| Thu 1 Oct | 30040 23:02 | 0 min | +4 min |
| Wed 30 Sept | 30040 22:59 | −2 min | +5 min |
| Tue 29 Sept | 30040 23:01 | −1 min | +4 min |
| Mon 28 Sept | 30040 13:00 | +2 min | +4 min |
| Sun 27 Sept | 30040 18:30 | −2 min | +3 min |
| Sat 26 Sept | 30040 23:00 | −2 min | +7 min |
| Fri 25 Sept | 30040 23:00 | −2 min | +9 min |
| Thu 24 Sept | 30040 23:00 | −2 min | +3 min |
| Tue 22 Sept | 30331 22:12 | +11 min | +12 min |
| Mon 21 Sept | 30040 23:01 | −1 min | +6 min |
| Sun 20 Sept | 30040 18:30 | −2 min | +2 min |
| Sat 19 Sept | 30040 23:07 | +6 min | +9 min |
| Fri 18 Sept | 30040 23:05 | +4 min | +9 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.