Os 24712 24712 Prostějov hl. n. – Dzbel
Alerts for train 24712
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 24712.
It has not run yet today
Last recorded run: Sunday 8 November No data
Next service: today 13:05 from Prostějov hl. n. · Mon 9 Nov
Last 30 days
Arrival delay at Dzbel, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 23 Sept Max en route +5 min · last fix heading to — +5 min
- Fri 2 Oct Max en route +6 min · last fix heading to — +4 min
- Mon 5 Oct Max en route +4 min · last fix heading to — +3 min
- Thu 1 Oct Max en route +6 min · last fix heading to — +3 min
- Fri 11 Sept Max en route +6 min · last fix heading to — +3 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 89% · 49
- 3–10 min 11% · 6
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=7
- 88% W n=8
- 88% T n=8
- 75% F n=8
- 88% S n=8
- 100% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (12 stops).
Last 90 days, 55 runs. At intermediate stops it is an estimate from the delay at origin and destination. Delays over 2 h count as “> 2 h”: our data does not measure them exactly.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 13:05 | on time | +5 min | |
| 13:08 / 13:09 | ≈ on time | ≈ +5 min | |
| 13:15 / 13:16 | ≈ on time | ≈ +4 min | |
| 13:19 | ≈ on time | ≈ +4 min | |
| 13:24 | ≈ on time | ≈ +4 min | |
| 13:28 / 13:31 | ≈ on time | ≈ +3 min | |
| 13:35 | ≈ on time | ≈ +3 min | |
| 13:39 | ≈ on time | ≈ +3 min | |
| 13:41 | ≈ on time | ≈ +3 min | |
| 13:46 / 13:47 | ≈ on time | ≈ +3 min | |
| 13:51 | ≈ on time | ≈ +3 min | |
| 13:54 | on time | +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.
Will I make my connection?
Pick where you get off and how many minutes you have until your next train. We work it out from what this train did over the last 90 days.
Include the time to change platforms. It is an estimate from past data, not a guarantee. Days more than 2 h late count as a missed connection.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sun 8 Nov | Dzbel 13:54 | No data | — |
| Sat 7 Nov | Dzbel 13:54 | No data | — |
| Fri 6 Nov | Dzbel 13:54 | No data | — |
| Thu 5 Nov | Dzbel 13:54 | No data | — |
| Wed 4 Nov | Dzbel 13:55 | No data | — |
| Tue 3 Nov | Dzbel 13:54 | No data | — |
| Mon 2 Nov | Dzbel 13:54 | No data | — |
| Sun 1 Nov | Dzbel 13:55 | No data | — |
| Sat 31 Oct | Dzbel 13:55 | No data | — |
| Fri 30 Oct | Dzbel 13:55 | No data | — |
| Thu 29 Oct | Dzbel 13:55 | No data | — |
| Wed 28 Oct | Dzbel 13:55 | No data | — |
| Tue 27 Oct | Dzbel 13:55 | No data | — |
| Mon 26 Oct | Dzbel 13:55 | No data | — |
| Sun 25 Oct | Dzbel 13:55 | No data | — |
| Sat 24 Oct | Dzbel 13:55 | No data | — |
| Fri 23 Oct | Dzbel 13:55 | No data | — |
| Thu 22 Oct | Dzbel 13:55 | No data | — |
| Wed 21 Oct | Dzbel 13:55 | No data | — |
| Tue 20 Oct | Dzbel 13:55 | No data | — |
| Mon 19 Oct | Dzbel 13:55 | No data | — |
| Sun 18 Oct | Dzbel 13:55 | No data | — |
| Sat 17 Oct | Dzbel 13:55 | No data | — |
| Fri 16 Oct | Dzbel 13:55 | No data | — |
| Thu 15 Oct | Dzbel 13:55 | No data | — |
| Wed 14 Oct | Dzbel 13:55 | No data | — |
| Tue 13 Oct | Dzbel 13:55 | No data | — |
| Mon 12 Oct | Dzbel 13:55 | No data | — |
| Sun 11 Oct | Dzbel 13:55 | No data | — |
| Sat 10 Oct | Dzbel 13:55 | No data | — |