Os 24156 24156 Moravský Písek – Bzenec

View line Os 24156

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

Running now · updated 19:21

Between Bzenec-Olšovec and Bzenec No data

Estimated arrival at Bzenec 19:20 · 40 km/h

  1. Moravský Písek19:14
  2. Bzenec-Olšovec19:17
  3. Bzenec19:20
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
80%
43/54 runs under 3 min
RT coverage: 54 full · 0 partial · 36 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
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 31 Aug Max en route +9 min · last fix heading to — +8 min
  • Mon 17 Aug Max en route +8 min · last fix heading to — +7 min
  • Tue 29 Sept Max en route +5 min · last fix heading to — +5 min
  • Fri 11 Sept Max en route +4 min · last fix heading to — +4 min
  • Wed 2 Sept Max en route +6 min · last fix heading to — +4 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 80% · 43
  • 3–10 min 20% · 11
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 71% M n=7
  • 57% T n=7
  • 75% W n=8
  • 88% T n=8
  • 88% F n=8
  • 88% S n=8
  • 88% 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 10Today
19:14on time +4 minPassed
19:17≈ on time ≈ +4 minPassed
19:20on time +4 minNext

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