Os 18130 18130 Lenora – Volary

View line Os 18130

Lenora 06:18 → Volary 06:32 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Volary at 06:33 No data

  1. Lenora06:18
  2. Lenora zastávka06:20
  3. Soumarský Most06:24
  4. Volary06:32

Next service: tomorrow 06:18 from Lenora · Fri 6 Nov

Next departure 06:18 tomorrow · Lenora
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 20 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 Volary, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 24
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
06:18on time on time
06:20≈ on time ≈ on time
06:24≈ on time ≈ +1 min
06:32on 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
Thu 5 NovVolary 06:33No data—
Wed 4 NovVolary 06:33No data—
Tue 3 NovVolary 06:33No data—
Mon 2 NovVolary 06:33No data—
Tue 27 OctVolary 06:33No data—
Mon 26 OctVolary 06:33No data—
Fri 23 OctVolary 06:33No data—
Thu 22 OctVolary 06:33No data—
Wed 21 OctVolary 06:33No data—
Tue 20 OctVolary 06:33No data—
Mon 19 OctVolary 06:33No data—
Fri 16 OctVolary 06:33No data—
Thu 15 OctVolary 06:33No data—
Wed 14 OctVolary 06:33No data—
Tue 13 OctVolary 06:33No data—
Mon 12 OctVolary 06:33No data—
Fri 9 OctVolary 06:33No data—
Thu 8 OctVolary 06:33No data—
Wed 7 OctVolary 06:33No data—
Tue 6 OctVolary 06:33No data—
Mon 5 Oct— 06:470 min—
Fri 2 Oct— 06:48+1 min+1 min
Thu 1 Oct— 06:49+2 min+2 min
Wed 30 Sept— 06:47+1 min+1 min
Tue 29 Sept— 06:460 min—
Fri 25 Sept— 06:470 min—
Thu 24 Sept— 06:48+2 min+2 min
Wed 23 Sept— 06:47+1 min+1 min
Tue 22 Sept— 06:49+2 min+2 min
Mon 21 Sept— 06:49+2 min+2 min