Os 24141 24141 Bzenec – Moravský Písek

View line Os 24141

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

✓ Today’s run finished

Today, last fix heading to Moravský Písek at 15:44 No data

  1. Bzenec15:39
  2. Bzenec-Olšovec15:42
  3. Moravský Písek15:45

Next service: tomorrow 15:39 from Bzenec · Mon 9 Nov

Next departure 15:39 tomorrow · Bzenec
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
100%
56/56 runs under 3 min
RT coverage: 56 full · 0 partial · 34 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 Moravský Písek, 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

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

  • Early 4% · 2
  • On time 96% · 54
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=8
  • 100% T n=8
  • 100% F n=8
  • 100% 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, 56 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
15:39on time on time
15:42≈ on time ≈ on time
15:45on 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 NovMoravský Písek 15:44No data—
Sat 7 NovMoravský Písek 15:45No data—
Fri 6 NovMoravský Písek 15:44No data—
Thu 5 NovMoravský Písek 15:44No data—
Wed 4 NovMoravský Písek 15:45No data—
Tue 3 NovMoravský Písek 15:44No data—
Mon 2 NovMoravský Písek 15:44No data—
Sun 1 NovMoravský Písek 15:46No data—
Sat 31 OctMoravský Písek 15:46No data—
Fri 30 OctMoravský Písek 15:46No data—
Thu 29 OctMoravský Písek 15:46No data—
Wed 28 OctMoravský Písek 15:46No data—
Tue 27 OctMoravský Písek 15:46No data—
Mon 26 OctMoravský Písek 15:46No data—
Sun 25 OctMoravský Písek 15:46No data—
Sat 24 OctMoravský Písek 15:46No data—
Fri 23 OctMoravský Písek 15:46No data—
Thu 22 OctMoravský Písek 15:46No data—
Wed 21 OctMoravský Písek 15:46No data—
Tue 20 OctMoravský Písek 15:46No data—
Mon 19 OctMoravský Písek 15:46No data—
Sun 18 OctMoravský Písek 15:46No data—
Sat 17 OctMoravský Písek 15:46No data—
Fri 16 OctMoravský Písek 15:46No data—
Thu 15 OctMoravský Písek 15:46No data—
Wed 14 OctMoravský Písek 15:46No data—
Tue 13 OctMoravský Písek 15:46No data—
Mon 12 OctMoravský Písek 15:46No data—
Sun 11 OctMoravský Písek 15:46No data—
Sat 10 OctMoravský Písek 15:46No data—