Train regional 862Q12
It does not run today
Last recorded run: Tuesday 6 October −4 min
The mini-map returns when the train runs
On-time · 30 days
33%
1/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
67%
4/6 runs under 3 min
RT coverage: 6 full · 0 partial · 0 no data
Typical delay
−2min
Median at arrival, 90 days
P90
+68min
9 in 10 runs arrive with less than this
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 21 Sept Max en route +106 min · last fix heading to 86322 +93 min
- Mon 5 Oct Max en route +42 min · last fix heading to — +42 min
Distribution · 90 days
6 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 50% · 3
- On time 17% · 1
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 33% · 2
On-time by weekday
- 60% M n=5
- 100% T n=1
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Tue 6 Oct | — 01:44 | −4 min | — |
| Mon 5 Oct | — 14:12 | +42 min | +42 min |
| Mon 21 Sept | 86322 15:50 | +93 min | +106 min |
| Mon 7 Sept | 86322 12:57 | −40 min | — |
| Mon 24 Aug | 86322 15:08 | 0 min | — |
| Mon 10 Aug | 86322 15:22 | −4 min | +68 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.