Os 23249 23249 Horní Lideč – Bylnice

View line Os 23249

Horní Lideč 22:20 → Bylnice 22:45 Daily 0 h 25 min · 8 stops ARRIVA vlaky s.r.o.

It has not run yet today

Last recorded run: Saturday 7 November No data

Next service: today 22:20 from Horní Lideč · Sun 8 Nov

Next departure 22:20 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
83%
5/6 runs under 3 min
RT coverage: 6 full · 0 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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

  • Mon 21 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=1
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 100% S n=1
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 stops).

Last 90 days, 6 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
22:20on time on time
22:23≈ on time ≈ on time
22:26≈ on time ≈ on time
22:28 / 22:29≈ on time ≈ on time
22:35≈ on time ≈ +1 min
22:37 / 22:38≈ on time ≈ +1 min
22:40≈ on time ≈ +1 min
22:45on 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

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