Train regional 42Q24
It does not run today
Last recorded run: Monday 5 October +3 min
The mini-map returns when the train runs
On-time · 30 days
—
Too little data (2/2 runs with data)
RT coverage: 2 full · 0 partial · 0 no data
On-time · 90 days
50%
2/4 runs under 3 min
RT coverage: 4 full · 0 partial · 0 no data
Typical delay
—
Needs at least 5 runs with data (4 so far)
P90
—
Needs at least 5 runs with data (4 so far)
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 7 Sept Max en route +58 min · last fix heading to 04111 +6 min
- Mon 5 Oct Max en route +3 min · last fix heading to Manchester Victoria +3 min
Distribution · 90 days
4 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 25% · 1
- On time 25% · 1
- 3–10 min 50% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=4
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | Manchester Victoria 22:47 | +3 min | +3 min |
| Mon 28 Sept | 04111 21:56 | +1 min | +4 min |
| Mon 14 Sept | 57406 21:59 | −11 min | +13 min |
| Mon 7 Sept | 04111 22:49 | +6 min | +58 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.