Os 4245 4245 Moravský Písek – Hulín
Alerts for train 4245
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 4245.
✓ Today’s run finished
Today, last fix heading to Hulín at 05:24 No data
- Moravský Písek04:35
- Nedakonice04:43
- St. Město u U.H.04:49
- Spytihněv04:59
- Napajedla05:02
- Tlumačov05:14
- Hulín05:23
Next service: tomorrow 04:35 from Moravský Písek · Tue 10 Nov
Last 30 days
Arrival delay at Hulín, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 24 Sept Max en route +8 min · last fix heading to — +3 min
- Mon 21 Sept Max en route +10 min · last fix heading to — +3 min
Distribution · 90 days
55 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 53% · 29
- On time 44% · 24
- 3–10 min 4% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=7
- 100% W n=8
- 88% 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 (12 stops).
Last 90 days, 55 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 |
|---|---|---|---|
| 04:35 | on time | on time | |
| 04:37 / 04:38 | ≈ on time | ≈ on time | |
| 04:43 | ≈ on time | ≈ on time | |
| 04:46 | ≈ on time | ≈ on time | |
| 04:49 / 04:50 | ≈ on time | ≈ on time | |
| 04:55 / 04:56 | ≈ on time | ≈ +1 min | |
| 04:59 / 05:00 | ≈ on time | ≈ +1 min | |
| 05:02 / 05:03 | ≈ 1 min early | ≈ on time | |
| 05:08 / 05:09 | ≈ 1 min early | ≈ on time | |
| 05:14 / 05:15 | ≈ 1 min early | ≈ on time | |
| 05:18 / 05:19 | ≈ 1 min early | ≈ on time | |
| 05:23 | 2 min early | 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Mon 9 Nov | Hulín 05:24 | No data | — |
| Sun 8 Nov | Hulín 05:24 | No data | — |
| Sat 7 Nov | Hulín 05:24 | No data | — |
| Fri 6 Nov | Hulín 05:24 | No data | — |
| Thu 5 Nov | Hulín 05:24 | No data | — |
| Wed 4 Nov | Hulín 05:24 | No data | — |
| Tue 3 Nov | Hulín 05:25 | No data | — |
| Mon 2 Nov | Hulín 05:24 | No data | — |
| Sun 1 Nov | Hulín 05:24 | No data | — |
| Sat 31 Oct | Hulín 05:24 | No data | — |
| Fri 30 Oct | Hulín 05:24 | No data | — |
| Thu 29 Oct | Hulín 05:24 | No data | — |
| Wed 28 Oct | Hulín 05:25 | No data | — |
| Tue 27 Oct | Hulín 05:24 | No data | — |
| Mon 26 Oct | Hulín 05:24 | No data | — |
| Sun 25 Oct | Hulín 05:24 | No data | — |
| Sat 24 Oct | Hulín 05:24 | No data | — |
| Fri 23 Oct | Hulín 05:24 | No data | — |
| Thu 22 Oct | Hulín 05:24 | No data | — |
| Wed 21 Oct | Hulín 05:24 | No data | — |
| Tue 20 Oct | Hulín 05:24 | No data | — |
| Mon 19 Oct | Hulín 05:24 | No data | — |
| Sun 18 Oct | Hulín 05:24 | No data | — |
| Sat 17 Oct | Hulín 05:24 | No data | — |
| Fri 16 Oct | Hulín 05:24 | No data | — |
| Thu 15 Oct | Hulín 05:24 | No data | — |
| Wed 14 Oct | Hulín 05:24 | No data | — |
| Tue 13 Oct | Hulín 05:24 | No data | — |
| Mon 12 Oct | Hulín 05:24 | No data | — |
| Sun 11 Oct | Hulín 05:24 | No data | — |