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

View line Os 24733

Dzbel 06:05 → Prostějov hl. n. 06:53 Tue, Sat, Sun 0 h 48 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Prostějov hl. n. at 06:54 No data

  1. Dzbel06:05
  2. Konice06:11
  3. Čunín06:18
  4. Ptení06:27
  5. Zdětín u Prostějova06:34
  6. Kostelec na Hané06:42
  7. Prostějov hl. n.06:53

Next service: tomorrow 06:05 from Dzbel · Sun 15 Nov

Next departure 06:05 tomorrow · Dzbel
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 12 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 Prostějov hl. n., in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 15 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
06:05on time on time
06:07≈ on time ≈ on time
06:11 / 06:12≈ on time ≈ on time
06:16≈ on time ≈ on time
06:18≈ on time ≈ on time
06:22≈ on time ≈ on time
06:27 / 06:30≈ on time ≈ on time
06:34≈ on time ≈ on time
06:38≈ on time ≈ on time
06:42 / 06:43≈ on time ≈ on time
06:49 / 06:50≈ on time ≈ on time
06:53on 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
Sat 14 NovProstějov hl. n. 06:54No data—
Sun 8 NovProstějov hl. n. 06:54No data—
Sat 7 NovProstějov hl. n. 06:54No data—
Sun 1 NovProstějov hl. n. 06:54No data—
Sat 31 OctProstějov hl. n. 06:54No data—
Wed 28 OctProstějov hl. n. 06:54No data—
Sun 25 OctProstějov hl. n. 06:54No data—
Sat 24 OctProstějov hl. n. 06:54No data—
Sun 18 OctProstějov hl. n. 06:54No data—
Sat 17 OctProstějov hl. n. 06:54No data—
Sun 11 OctProstějov hl. n. 06:54No data—
Sat 10 OctProstějov hl. n. 06:54No data—
Sun 4 Oct— 07:080 min—
Sat 3 Oct— 07:080 min—
Mon 28 Sept— 07:080 min—
Sun 27 Sept— 07:080 min—
Sat 26 Sept— 07:070 min—
Sun 20 Sept— 07:070 min—
Sat 19 Sept— 07:080 min+1 min
Sun 13 Sept— 07:070 min—
Sat 12 Sept— 07:080 min—
Sun 6 Sept— 07:070 min—
Sat 5 Sept— 07:070 min—
Sun 30 Aug— 07:070 min—
Sat 29 Aug— 07:080 min—
Sun 23 Aug— 07:070 min—
Sat 22 Aug— 07:070 min—