Train regional 572Q11
It does not run today
Last recorded run: Monday 5 October −8 min
The mini-map returns when the train runs
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 3 full · 0 partial · 0 no data
On-time · 90 days
57%
4/7 runs under 3 min
RT coverage: 7 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
P90
+12min
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 31 Aug Max en route +14 min · last fix heading to — +14 min
- Sun 16 Aug Max en route +34 min · last fix heading to 50050 +10 min
- Sun 9 Aug Max en route +13 min · last fix heading to 70021 +6 min
Distribution · 90 days
7 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 43% · 3
- On time 14% · 1
- 3–10 min 14% · 1
- 10–30 min 29% · 2
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- 60% S n=5
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 5 Oct | — 02:10 | −8 min | — |
| Sun 4 Oct | 45128 00:37 | −4 min | +3 min |
| Sun 27 Sept | 23418 15:47 | −11 min | +3 min |
| Mon 31 Aug | — 10:31 | +14 min | +14 min |
| Sun 30 Aug | 74802 22:07 | 0 min | +15 min |
| Sun 16 Aug | 50050 14:58 | +10 min | +34 min |
| Sun 9 Aug | 70021 17:14 | +6 min | +13 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.