Os 24104 24104 Moravský Písek – Bzenec
Alerts for train 24104
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line Os 24104.
✓ Today’s run finished
Today, last fix heading to Bzenec at 05:19 No data
- Moravský Písek05:14
- Bzenec-Olšovec05:17
- Bzenec05:20
Next service: tomorrow 05:14 from Moravský Písek · Tue 10 Nov
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
- Fri 18 Sept Max en route +11 min · last fix heading to — +10 min
- Tue 15 Sept Max en route +11 min · last fix heading to — +10 min
- Fri 25 Sept Max en route +11 min · last fix heading to — +9 min
- Wed 23 Sept Max en route +10 min · last fix heading to — +9 min
- Thu 24 Sept Max en route +9 min · last fix heading to — +8 min
Distribution · 90 days
38 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 5% · 2
- On time 68% · 26
- 3–10 min 21% · 8
- 10–30 min 5% · 2
- 30+ min 0% · 0
On-time by weekday
- 71% M n=7
- 71% T n=7
- 75% W n=8
- 75% T n=8
- 75% 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, 38 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 05:14 | +1 min | +9 min | |
| 05:17 | ≈ on time | ≈ +9 min | |
| 05:20 | on time | +8 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Bzenec 05:19 | No data | — |
| Fri 6 Nov | Bzenec 05:19 | No data | — |
| Thu 5 Nov | Bzenec 05:19 | No data | — |
| Wed 4 Nov | Bzenec 05:19 | No data | — |
| Tue 3 Nov | Bzenec 05:20 | No data | — |
| Mon 2 Nov | Bzenec 05:19 | No data | — |
| Fri 30 Oct | Bzenec 05:21 | No data | — |
| Thu 29 Oct | Bzenec 05:21 | No data | — |
| Tue 27 Oct | Bzenec 05:21 | No data | — |
| Mon 26 Oct | Bzenec 05:21 | No data | — |
| Fri 23 Oct | Bzenec 05:21 | No data | — |
| Thu 22 Oct | Bzenec 05:21 | No data | — |
| Wed 21 Oct | Bzenec 05:21 | No data | — |
| Tue 20 Oct | Bzenec 05:21 | No data | — |
| Mon 19 Oct | Bzenec 05:21 | No data | — |
| Fri 16 Oct | Bzenec 05:21 | No data | — |
| Thu 15 Oct | Bzenec 05:21 | No data | — |
| Wed 14 Oct | Bzenec 05:21 | No data | — |
| Tue 13 Oct | Bzenec 05:21 | No data | — |
| Mon 12 Oct | Bzenec 05:21 | No data | — |
| Fri 9 Oct | Bzenec 05:21 | No data | — |
| Thu 8 Oct | Bzenec 05:21 | No data | — |
| Wed 7 Oct | Bzenec 05:21 | No data | — |
| Tue 6 Oct | Bzenec 05:21 | No data | — |
| Mon 5 Oct | — 05:35 | 0 min | — |
| Fri 2 Oct | — 05:34 | 0 min | — |
| Thu 1 Oct | — 05:34 | 0 min | — |
| Wed 30 Sept | — 05:34 | 0 min | +1 min |
| Tue 29 Sept | — 05:33 | −1 min | — |
| Fri 25 Sept | — 05:43 | +9 min | +11 min |