Os 20601 20601 Liptaň – Osoblaha

View line Os 20601

Liptaň 07:38 → Osoblaha 08:17 Mon, Tue, Wed, Thu, Fri, Sat 0 h 39 min · 8 stops Osoblažská úzkorozchodná dráha o.p.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 07:38 from Liptaň · Sat 7 Nov

Next departure 07:38 today · Liptaň
On-time · 30 days
—
Too little data (0/25 runs with data)
RT coverage: 0 full · 0 partial · 25 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 28 no data
Typical delay
−1min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Osoblaha, 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 5 Oct Max en route +13 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 40% · 19
  • On time 58% · 28
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 48 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
07:38on time on time
07:45≈ on time ≈ on time
07:48≈ on time ≈ on time
07:52≈ on time ≈ on time
07:55 / 07:56≈ on time ≈ on time
08:02≈ 1 min early ≈ on time
08:08 / 08:09≈ 1 min early ≈ on time
08:171 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

DateLast stopFinalMax
Fri 6 NovOsoblaha 08:18No data—
Thu 5 NovOsoblaha 08:18No data—
Wed 4 NovOsoblaha 08:18No data—
Tue 3 NovOsoblaha 08:18No data—
Mon 2 NovOsoblaha 08:18No data—
Sat 31 OctOsoblaha 08:18No data—
Fri 30 OctOsoblaha 08:18No data—
Thu 29 OctOsoblaha 08:18No data—
Wed 28 OctOsoblaha 08:18No data—
Tue 27 OctOsoblaha 08:18No data—
Mon 26 OctOsoblaha 08:18No data—
Sat 24 OctOsoblaha 08:18No data—
Fri 23 OctOsoblaha 08:18No data—
Thu 22 OctOsoblaha 08:19No data—
Wed 21 OctOsoblaha 08:18No data—
Tue 20 OctOsoblaha 08:18No data—
Mon 19 OctOsoblaha 08:18No data—
Sat 17 OctOsoblaha 08:18No data—
Fri 16 OctOsoblaha 08:18No data—
Thu 15 OctOsoblaha 08:18No data—
Wed 14 OctOsoblaha 08:18No data—
Tue 13 OctOsoblaha 08:18No data—
Mon 12 OctOsoblaha 08:18No data—
Sat 10 OctOsoblaha 08:18No data—
Fri 9 OctOsoblaha 08:18No data—
Thu 8 OctOsoblaha 08:18No data—
Wed 7 OctOsoblaha 08:18No data—
Tue 6 OctOsoblaha 08:18No data—
Mon 5 Oct— 08:35+3 min+13 min
Sat 3 Oct— 08:310 min—