Os 24714 24714 Prostějov hl. n. – Dzbel

View line Os 24714

Prostějov hl. n. 14:05 → Dzbel 14:54 Mon, Tue, Wed, Thu, Fri 0 h 49 min · 12 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 14:05 from Prostějov hl. n. · Mon 9 Nov

Next departure 14:05 today · Prostějov hl. n.
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
95%
35/37 runs under 3 min
RT coverage: 37 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

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

  • Fri 11 Sept Max en route +6 min · last fix heading to — +3 min
  • Fri 28 Aug Max en route +5 min · last fix heading to — +3 min

Distribution · 90 days

37 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 95% · 35
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 stops).

Last 90 days, 37 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.

StopSched.Usually 9 days in 10
14:05on time +2 min
14:08 / 14:09≈ on time ≈ +2 min
14:15 / 14:16≈ on time ≈ +1 min
14:19≈ on time ≈ +1 min
14:24≈ on time ≈ +1 min
14:28 / 14:31≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:39≈ on time ≈ +1 min
14:41≈ on time ≈ +1 min
14:46 / 14:47≈ on time ≈ on time
14:51≈ on time ≈ on time
14:54on time on time

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

DateLast stopFinalMax
Fri 6 NovDzbel 14:54No data—
Thu 5 NovDzbel 14:54No data—
Wed 4 NovDzbel 14:55No data—
Tue 3 NovDzbel 14:54No data—
Mon 2 NovDzbel 14:54No data—
Fri 30 OctDzbel 14:55No data—
Thu 29 OctDzbel 14:55No data—
Tue 27 OctDzbel 14:55No data—
Mon 26 OctDzbel 14:55No data—
Fri 23 OctDzbel 14:55No data—
Thu 22 OctDzbel 14:55No data—
Wed 21 OctDzbel 14:55No data—
Tue 20 OctDzbel 14:55No data—
Mon 19 OctDzbel 14:55No data—
Fri 16 OctDzbel 14:55No data—
Thu 15 OctDzbel 14:55No data—
Wed 14 OctDzbel 14:55No data—
Tue 13 OctDzbel 14:55No data—
Mon 12 OctDzbel 14:55No data—
Fri 9 OctDzbel 14:55No data—
Thu 8 OctDzbel 14:55No data—
Wed 7 OctDzbel 14:55No data—
Tue 6 OctDzbel 14:55No data—
Mon 5 Oct— 15:120 min—
Fri 2 Oct— 15:080 min—
Thu 1 Oct— 15:090 min—
Wed 30 Sept— 15:090 min—
Tue 29 Sept— 15:080 min—
Fri 25 Sept— 15:10+1 min+1 min
Thu 24 Sept— 15:080 min—