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

View line Os 24722

Prostějov hl. n. 19:05 → Dzbel 19:54 Daily 0 h 49 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Dzbel at 19:54 No data

  1. Prostějov hl. n.19:05
  2. Kostelec na Hané19:15
  3. Zdětín u Prostějova19:24
  4. Stražisko19:35
  5. Čunín19:39
  6. Konice19:46
  7. Dzbel19:54

Next service: tomorrow 19:05 from Prostějov hl. n. · Sat 7 Nov

Next departure 19:05 tomorrow · Prostějov hl. n.
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
95%
54/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

  • Sat 22 Aug Max en route +7 min · last fix heading to — +6 min
  • Wed 2 Sept Max en route +10 min · last fix heading to — +5 min
  • Sun 23 Aug Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 88% W n=8
  • 100% T n=8
  • 100% F n=8
  • 88% S n=8
  • 89% S n=9

Stops and timetable

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

Last 90 days, 57 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
19:05on time +4 min
19:08 / 19:09≈ on time ≈ +4 min
19:15 / 19:16≈ on time ≈ +4 min
19:19≈ on time ≈ +3 min
19:24≈ on time ≈ +3 min
19:28 / 19:31≈ on time ≈ +3 min
19:35≈ on time ≈ +2 min
19:39≈ on time ≈ +2 min
19:41≈ on time ≈ +2 min
19:46 / 19:47≈ on time ≈ +1 min
19:51≈ on time ≈ +1 min
19:54on time +1 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

DateLast stopFinalMax
Fri 6 NovDzbel 19:54No data—
Thu 5 NovDzbel 19:54No data—
Wed 4 NovDzbel 19:54No data—
Tue 3 NovDzbel 19:54No data—
Mon 2 NovDzbel 19:54No data—
Sun 1 NovDzbel 19:54No data—
Sat 31 OctDzbel 19:55No data—
Fri 30 OctDzbel 19:55No data—
Thu 29 OctDzbel 19:55No data—
Wed 28 OctDzbel 19:55No data—
Tue 27 OctDzbel 19:56No data—
Mon 26 OctDzbel 19:55No data—
Sun 25 OctDzbel 19:55No data—
Sat 24 OctDzbel 19:55No data—
Fri 23 OctDzbel 19:55No data—
Thu 22 OctDzbel 19:55No data—
Wed 21 OctDzbel 19:55No data—
Tue 20 OctDzbel 19:55No data—
Mon 19 OctDzbel 19:55No data—
Sun 18 OctDzbel 19:55No data—
Sat 17 OctDzbel 19:55No data—
Fri 16 OctDzbel 19:55No data—
Thu 15 OctDzbel 19:55No data—
Wed 14 OctDzbel 19:55No data—
Tue 13 OctDzbel 19:55No data—
Mon 12 OctDzbel 19:56No data—
Sun 11 OctDzbel 19:55No data—
Sat 10 OctDzbel 19:55No data—
Fri 9 OctDzbel 19:55No data—
Thu 8 OctDzbel 19:55No data—