Os 24108 24108 Moravský Písek – Bzenec

View line Os 24108

Moravský Písek 06:14 → Bzenec 06:20 Mon, Tue, Wed, Thu, Fri 0 h 06 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Bzenec at 06:19 No data

  1. Moravský Písek06:14
  2. Bzenec-Olšovec06:17
  3. Bzenec06:20

Next service: tomorrow 06:14 from Moravský Písek · Tue 10 Nov

Next departure 06:14 tomorrow · Moravský Písek
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 24 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 Bzenec, in minutes. One bar per run.

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

Worst days

  • Thu 27 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 97% · 36
  • 3–10 min 3% · 1
  • 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
  • 88% T n=8
  • 100% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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
06:14on time +2 min
06:17≈ on time ≈ +2 min
06:20on 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
Mon 9 NovBzenec 06:19No data—
Fri 6 NovBzenec 06:19No data—
Thu 5 NovBzenec 06:19No data—
Wed 4 NovBzenec 06:19No data—
Tue 3 NovBzenec 06:20No data—
Mon 2 NovBzenec 06:19No data—
Fri 30 OctBzenec 06:21No data—
Thu 29 OctBzenec 06:21No data—
Tue 27 OctBzenec 06:21No data—
Mon 26 OctBzenec 06:21No data—
Fri 23 OctBzenec 06:21No data—
Thu 22 OctBzenec 06:21No data—
Wed 21 OctBzenec 06:21No data—
Tue 20 OctBzenec 06:21No data—
Mon 19 OctBzenec 06:21No data—
Fri 16 OctBzenec 06:21No data—
Thu 15 OctBzenec 06:21No data—
Wed 14 OctBzenec 06:21No data—
Tue 13 OctBzenec 06:21No data—
Mon 12 OctBzenec 06:21No data—
Fri 9 OctBzenec 06:21No data—
Thu 8 OctBzenec 06:21No data—
Wed 7 OctBzenec 06:21No data—
Tue 6 OctBzenec 06:22No data—
Mon 5 Oct— 06:340 min—
Fri 2 Oct— 06:350 min—
Thu 1 Oct— 06:350 min—
Wed 30 Sept— 06:340 min—
Tue 29 Sept— 06:350 min+2 min
Fri 25 Sept— 06:340 min—