Os 24114 24114 Moravský Písek – Bzenec
Alerts for train 24114
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 24114.
✓ Today’s run finished
Today, last fix heading to Bzenec at 08:14 No data
- Moravský Písek08:07
- Bzenec-Olšovec08:10
- Bzenec08:13
Next service: tomorrow 08:07 from Moravský Písek · Sun 15 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
- Mon 14 Sept Max en route +10 min · last fix heading to — +10 min
- Wed 9 Sept Max en route +10 min · last fix heading to — +10 min
- Mon 5 Oct Max en route +9 min · last fix heading to — +8 min
- Fri 2 Oct Max en route +8 min · last fix heading to — +8 min
- Thu 1 Oct Max en route +9 min · last fix heading to — +8 min
Distribution · 90 days
50 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 36% · 18
- 3–10 min 60% · 30
- 10–30 min 4% · 2
- 30+ min 0% · 0
On-time by weekday
- 38% M n=8
- 0% T n=7
- 14% W n=7
- 14% T n=7
- 29% F n=7
- 57% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (3 stops).
Last 90 days, 50 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 |
|---|---|---|---|
| 08:07 | +5 min | +9 min | |
| 08:10 | ≈ +5 min | ≈ +9 min | |
| 08:13 | +4 min | +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 |
|---|---|---|---|
| Sat 14 Nov | Bzenec 08:14 | No data | — |
| Fri 13 Nov | Bzenec 08:14 | No data | — |
| Thu 12 Nov | Bzenec 08:14 | No data | — |
| Wed 11 Nov | Bzenec 08:14 | No data | — |
| Tue 10 Nov | Bzenec 08:14 | No data | — |
| Mon 9 Nov | Bzenec 08:14 | No data | — |
| Sun 8 Nov | Bzenec 08:14 | No data | — |
| Sat 7 Nov | Bzenec 08:14 | No data | — |
| Fri 6 Nov | Bzenec 08:14 | No data | — |
| Thu 5 Nov | Bzenec 08:14 | No data | — |
| Wed 4 Nov | Bzenec 08:14 | No data | — |
| Tue 3 Nov | Bzenec 08:14 | No data | — |
| Mon 2 Nov | Bzenec 08:14 | No data | — |
| Sun 1 Nov | Bzenec 08:14 | No data | — |
| Sat 31 Oct | Bzenec 08:14 | No data | — |
| Fri 30 Oct | Bzenec 08:14 | No data | — |
| Thu 29 Oct | Bzenec 08:14 | No data | — |
| Wed 28 Oct | Bzenec 08:14 | No data | — |
| Tue 27 Oct | Bzenec 08:14 | No data | — |
| Mon 26 Oct | Bzenec 08:14 | No data | — |
| Sun 25 Oct | Bzenec 08:14 | No data | — |
| Sat 24 Oct | Bzenec 08:14 | No data | — |
| Fri 23 Oct | Bzenec 08:14 | No data | — |
| Thu 22 Oct | Bzenec 08:15 | No data | — |
| Wed 21 Oct | Bzenec 08:14 | No data | — |
| Tue 20 Oct | Bzenec 08:14 | No data | — |
| Mon 19 Oct | Bzenec 08:14 | No data | — |
| Sun 18 Oct | Bzenec 08:14 | No data | — |
| Sat 17 Oct | Bzenec 08:14 | No data | — |
| Fri 16 Oct | Bzenec 08:14 | No data | — |