Os 23237 23237 Horní Lideč – Bylnice
Alerts for train 23237
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 23237.
✓ Today’s run finished
Today, last fix heading to Bylnice at 17:59 No data
- Horní Lideč17:33
- Valašské Příkazy17:36
- Poteč17:39
- Návojná17:48
- Brumov17:50
- Brumov střed17:53
- Bylnice17:58
Next service: tomorrow 17:33 from Horní Lideč · 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
- Tue 15 Sept Max en route +22 min · last fix heading to — +22 min
- Fri 18 Sept Max en route +7 min · last fix heading to — +7 min
- Sat 19 Sept Max en route +6 min · last fix heading to — +6 min
- Mon 21 Sept Max en route +5 min · last fix heading to — +5 min
- Mon 14 Sept Max en route +5 min · last fix heading to — +4 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 91% · 52
- 3–10 min 7% · 4
- 10–30 min 2% · 1
- 30+ min 0% · 0
On-time by weekday
- 75% M n=8
- 88% T n=8
- 100% W n=8
- 100% T n=8
- 88% F n=8
- 88% S n=8
- 100% S n=9
Stops and timetable
Timetable of the latest run from the operator’s GTFS (8 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 |
|---|---|---|---|
| 17:33 | on time | +3 min | |
| 17:36 | ≈ on time | ≈ +3 min | |
| 17:39 | ≈ on time | ≈ +2 min | |
| 17:41 / 17:42 | ≈ on time | ≈ +2 min | |
| 17:48 | ≈ on time | ≈ +2 min | |
| 17:50 / 17:51 | ≈ on time | ≈ +1 min | |
| 17:53 | ≈ on time | ≈ +2 min | |
| 17:58 | on time | +2 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 17:59 | No data | — |
| Thu 5 Nov | Bylnice 18:00 | No data | — |
| Wed 4 Nov | Bylnice 17:59 | No data | — |
| Tue 3 Nov | Bylnice 17:59 | No data | — |
| Mon 2 Nov | Bylnice 17:59 | No data | — |
| Sun 1 Nov | Bylnice 17:59 | No data | — |
| Sat 31 Oct | Bylnice 17:59 | No data | — |
| Fri 30 Oct | Bylnice 17:59 | No data | — |
| Thu 29 Oct | Bylnice 17:59 | No data | — |
| Wed 28 Oct | Bylnice 17:59 | No data | — |
| Tue 27 Oct | Bylnice 18:00 | No data | — |
| Mon 26 Oct | Bylnice 17:59 | No data | — |
| Sun 25 Oct | Bylnice 17:59 | No data | — |
| Sat 24 Oct | Bylnice 17:59 | No data | — |
| Fri 23 Oct | Bylnice 17:59 | No data | — |
| Thu 22 Oct | Bylnice 17:59 | No data | — |
| Wed 21 Oct | Bylnice 17:59 | No data | — |
| Tue 20 Oct | Bylnice 18:00 | No data | — |
| Mon 19 Oct | Bylnice 17:59 | No data | — |
| Sun 18 Oct | Bylnice 17:59 | No data | — |
| Sat 17 Oct | Bylnice 17:59 | No data | — |
| Fri 16 Oct | Bylnice 17:59 | No data | — |
| Thu 15 Oct | Bylnice 17:59 | No data | — |
| Wed 14 Oct | Bylnice 17:59 | No data | — |
| Tue 13 Oct | Bylnice 17:59 | No data | — |
| Mon 12 Oct | Bylnice 18:00 | No data | — |
| Sun 11 Oct | Bylnice 17:59 | No data | — |
| Sat 10 Oct | Bylnice 17:59 | No data | — |
| Fri 9 Oct | Bylnice 17:59 | No data | — |
| Thu 8 Oct | Bylnice 17:59 | No data | — |