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