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

View line Os 24734

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

✓ Today’s run finished

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

  1. Prostějov hl. n.07:05
  2. Kostelec na Hané07:15
  3. Zdětín u Prostějova07:24
  4. Stražisko07:35
  5. Čunín07:39
  6. Konice07:46
  7. Dzbel07:54

Next service: Saturday 07:05 from Prostějov hl. n. · Sat 14 Nov

Next departure 07:05 Saturday · Prostějov hl. n.
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 17
  • 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=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 17 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
07:05on time +2 min
07:08 / 07:09≈ on time ≈ +2 min
07:15 / 07:16≈ on time ≈ +2 min
07:19≈ on time ≈ +2 min
07:24≈ on time ≈ +1 min
07:28 / 07:31≈ on time ≈ +1 min
07:35≈ on time ≈ +1 min
07:39≈ on time ≈ +1 min
07:41≈ on time ≈ +1 min
07:46 / 07:47≈ on time ≈ on time
07:51≈ on time ≈ on time
07: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
Sun 8 NovDzbel 07:54No data—
Sat 7 NovDzbel 07:54No data—
Sun 1 NovDzbel 07:55No data—
Sat 31 OctDzbel 07:55No data—
Wed 28 OctDzbel 07:55No data—
Sun 25 OctDzbel 07:55No data—
Sat 24 OctDzbel 07:55No data—
Sun 18 OctDzbel 07:55No data—
Sat 17 OctDzbel 07:55No data—
Sun 11 OctDzbel 07:55No data—
Sat 10 OctDzbel 07:55No data—
Sun 4 Oct— 08:090 min—
Sat 3 Oct— 08:080 min—
Mon 28 Sept— 08:090 min—
Sun 27 Sept— 08:090 min—
Sat 26 Sept— 08:090 min—
Sun 20 Sept— 08:090 min—
Sat 19 Sept— 08:090 min—
Sun 13 Sept— 08:080 min—
Sat 12 Sept— 08:090 min—
Sun 6 Sept— 08:080 min—
Sat 5 Sept— 08:080 min+7 min
Sun 30 Aug— 08:080 min—
Sat 29 Aug— 08:090 min+6 min
Sun 23 Aug— 08:07−1 min—
Sat 22 Aug— 08:080 min—
Sun 16 Aug— 08:080 min—
Sat 15 Aug— 08:080 min—