Os 4383 4383 Uherský Brod – Bylnice
Alerts for train 4383
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 4383.
It has not run yet today
Last recorded run: Friday 6 November No data
Next service: today 05:28 from Uherský Brod · Sat 7 Nov
Last 30 days
Arrival delay at Bylnice, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 30 Sept Max en route +51 min · last fix heading to — +51 min
- Sat 3 Oct Max en route +26 min · last fix heading to — +22 min
- Fri 21 Aug Max en route +17 min · last fix heading to — +17 min
- Fri 4 Sept Max en route +15 min · last fix heading to — +15 min
- Mon 21 Sept Max en route +16 min · last fix heading to — +14 min
Distribution · 90 days
57 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 19% · 11
- 3–10 min 65% · 37
- 10–30 min 14% · 8
- 30+ min 2% · 1
On-time by weekday
- 0% M n=9
- 13% T n=8
- 0% W n=8
- 25% T n=8
- 25% F n=8
- 38% S n=8
- 38% S n=8
Stops and timetable
Timetable of the latest run from the operator’s GTFS (14 stops).
Last 90 days, 57 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:28 | +5 min | +9 min | |
| 05:31 / 05:32 | ≈ +5 min | ≈ +10 min | |
| 05:35 | ≈ +5 min | ≈ +11 min | |
| 05:38 | ≈ +5 min | ≈ +12 min | |
| 05:41 | ≈ +5 min | ≈ +12 min | |
| 05:44 / 05:45 | ≈ +5 min | ≈ +12 min | |
| 05:47 | ≈ +5 min | ≈ +12 min | |
| 05:50 | ≈ +5 min | ≈ +12 min | |
| 05:57 | ≈ +5 min | ≈ +12 min | |
| 06:02 / 06:03 | ≈ +5 min | ≈ +12 min | |
| 06:06 | ≈ +5 min | ≈ +12 min | |
| 06:08 / 06:09 | ≈ +5 min | ≈ +12 min | |
| 06:14 | ≈ +5 min | ≈ +13 min | |
| 06:19 | +5 min | +13 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 |
|---|---|---|---|
| Fri 6 Nov | Bylnice 06:19 | No data | — |
| Thu 5 Nov | Bylnice 06:19 | No data | — |
| Wed 4 Nov | Bylnice 06:19 | No data | — |
| Tue 3 Nov | Bylnice 06:20 | No data | — |
| Mon 2 Nov | Bylnice 06:19 | No data | — |
| Sun 1 Nov | Bylnice 06:20 | No data | — |
| Sat 31 Oct | Bylnice 06:20 | No data | — |
| Fri 30 Oct | Bylnice 06:20 | No data | — |
| Thu 29 Oct | Bylnice 06:20 | No data | — |
| Wed 28 Oct | Bylnice 06:20 | No data | — |
| Tue 27 Oct | Bylnice 06:20 | No data | — |
| Mon 26 Oct | Bylnice 06:20 | No data | — |
| Sun 25 Oct | Bylnice 06:20 | No data | — |
| Sat 24 Oct | Bylnice 06:20 | No data | — |
| Fri 23 Oct | Bylnice 06:20 | No data | — |
| Thu 22 Oct | Bylnice 06:20 | No data | — |
| Wed 21 Oct | Bylnice 06:20 | No data | — |
| Tue 20 Oct | Bylnice 06:20 | No data | — |
| Mon 19 Oct | Bylnice 06:20 | No data | — |
| Sun 18 Oct | Bylnice 06:20 | No data | — |
| Sat 17 Oct | Bylnice 06:20 | No data | — |
| Fri 16 Oct | Bylnice 06:20 | No data | — |
| Thu 15 Oct | Bylnice 06:20 | No data | — |
| Wed 14 Oct | Bylnice 06:20 | No data | — |
| Tue 13 Oct | Bylnice 06:20 | No data | — |
| Mon 12 Oct | Bylnice 06:20 | No data | — |
| Sun 11 Oct | Bylnice 06:20 | No data | — |
| Sat 10 Oct | Bylnice 06:20 | No data | — |
| Fri 9 Oct | Bylnice 06:20 | No data | — |
| Thu 8 Oct | Bylnice 06:20 | No data | — |