Os 23227 23227 Horní Lideč – Bylnice

View line Os 23227

Horní Lideč 14:33 → Bylnice 14:58 Daily 0 h 25 min · 8 stops ARRIVA vlaky s.r.o.

It has not run yet today

Last recorded run: Sunday 8 November No data

Next service: today 14:33 from Horní Lideč · Mon 9 Nov

Next departure 14:33 today · Horní Lideč
On-time · 30 days
—
Too little data (0/29 runs with data)
RT coverage: 0 full · 0 partial · 29 no data
On-time · 90 days
82%
45/55 runs under 3 min
RT coverage: 55 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
P90
+4min
9 in 10 runs arrive with less than this

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

  • Fri 18 Sept Max en route +19 min · last fix heading to — +19 min
  • Wed 30 Sept Max en route +13 min · last fix heading to — +12 min
  • Wed 16 Sept Max en route +14 min · last fix heading to — +12 min
  • Tue 15 Sept Max en route +11 min · last fix heading to — +11 min
  • Mon 14 Sept Max en route +9 min · last fix heading to — +9 min

Distribution · 90 days

55 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 82% · 45
  • 3–10 min 11% · 6
  • 10–30 min 7% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 86% T n=7
  • 63% W n=8
  • 88% T n=8
  • 75% F n=8
  • 88% S n=8
  • 100% S n=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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.

StopSched.Usually 9 days in 10
14:33on time +5 min
14:36≈ on time ≈ +5 min
14:39≈ on time ≈ +6 min
14:41 / 14:42≈ on time ≈ +5 min
14:48≈ on time ≈ +5 min
14:50 / 14:51≈ on time ≈ +5 min
14:53≈ on time ≈ +4 min
14:58on time +4 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

DateLast stopFinalMax
Sun 8 NovBylnice 14:59No data—
Sat 7 NovBylnice 14:59No data—
Fri 6 NovBylnice 14:59No data—
Thu 5 NovBylnice 14:59No data—
Wed 4 NovBylnice 15:00No data—
Tue 3 NovBylnice 14:59No data—
Mon 2 NovBylnice 14:59No data—
Sun 1 NovBylnice 14:59No data—
Sat 31 OctBylnice 14:59No data—
Fri 30 OctBylnice 14:59No data—
Thu 29 OctBylnice 14:59No data—
Wed 28 OctBylnice 14:59No data—
Tue 27 OctBylnice 14:59No data—
Mon 26 OctBylnice 14:59No data—
Sun 25 OctBylnice 14:59No data—
Sat 24 OctBylnice 14:59No data—
Fri 23 OctBylnice 14:59No data—
Thu 22 OctBylnice 14:59No data—
Wed 21 OctBylnice 14:59No data—
Tue 20 OctBylnice 14:59No data—
Mon 19 OctBylnice 14:59No data—
Sun 18 OctBylnice 14:59No data—
Sat 17 OctBylnice 14:59No data—
Fri 16 OctBylnice 14:59No data—
Thu 15 OctBylnice 14:59No data—
Wed 14 OctBylnice 14:59No data—
Tue 13 OctBylnice 14:59No data—
Mon 12 OctBylnice 14:59No data—
Sun 11 OctBylnice 14:59No data—
Sat 10 OctBylnice 14:59No data—