Os 24126 24126 Moravský Písek – Bzenec

View line Os 24126

Moravský Písek 12:07 → Bzenec 12:13 Daily 0 h 06 min · 3 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Monday 9 November No data

Next service: today 12:07 from Moravský Písek · Tue 10 Nov

Next departure 12:07 today · Moravský Písek
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
89%
48/54 runs under 3 min
RT coverage: 54 full · 0 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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

  • Mon 21 Sept Max en route +13 min · last fix heading to — +12 min
  • Thu 27 Aug Max en route +9 min · last fix heading to — +8 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 21 Aug Max en route +5 min · last fix heading to — +4 min
  • Sat 19 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 48
  • 3–10 min 9% · 5
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=7
  • 86% W n=7
  • 88% T n=8
  • 88% F n=8
  • 88% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 54 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
12:07on time +3 min
12:10≈ on time ≈ +2 min
12:13on time +3 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 12:14No data—
Sun 8 NovBzenec 12:14No data—
Sat 7 NovBzenec 12:14No data—
Fri 6 NovBzenec 12:14No data—
Thu 5 NovBzenec 12:14No data—
Wed 4 NovBzenec 12:14No data—
Tue 3 NovBzenec 12:14No data—
Mon 2 NovBzenec 12:14No data—
Sun 1 NovBzenec 12:14No data—
Sat 31 OctBzenec 12:14No data—
Fri 30 OctBzenec 12:14No data—
Thu 29 OctBzenec 12:14No data—
Wed 28 OctBzenec 12:14No data—
Tue 27 OctBzenec 12:14No data—
Mon 26 OctBzenec 12:14No data—
Sun 25 OctBzenec 12:14No data—
Sat 24 OctBzenec 12:14No data—
Fri 23 OctBzenec 12:14No data—
Thu 22 OctBzenec 12:14No data—
Wed 21 OctBzenec 12:14No data—
Tue 20 OctBzenec 12:14No data—
Mon 19 OctBzenec 12:14No data—
Sun 18 OctBzenec 12:14No data—
Sat 17 OctBzenec 12:14No data—
Fri 16 OctBzenec 12:14No data—
Thu 15 OctBzenec 12:14No data—
Wed 14 OctBzenec 12:14No data—
Tue 13 OctBzenec 12:14No data—
Mon 12 OctBzenec 12:14No data—
Sun 11 OctBzenec 12:14No data—