Os 18064 18064 Volary – Stožec

View line Os 18064

Volary 13:46 → Stožec 14:00 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops GW Train Regio a.s.

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 13:46 from Volary · Mon 9 Nov

Next departure 13:46 tomorrow · Volary
On-time · 30 days
—
Too little data (0/17 runs with data)
RT coverage: 0 full · 0 partial · 17 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 21 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Stožec, 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
13:46on time on time
13:50≈ on time ≈ on time
13:53 / 13:54≈ on time ≈ on time
14:00on time 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 NovStožec 13:59No data—
Thu 5 NovStožec 13:59No data—
Wed 4 NovStožec 14:00No data—
Tue 3 NovStožec 13:59No data—
Mon 2 NovStožec 13:59No data—
Tue 27 OctStožec 14:01No data—
Mon 26 OctStožec 14:01No data—
Fri 23 OctStožec 14:01No data—
Thu 22 OctStožec 14:01No data—
Wed 21 OctStožec 14:01No data—
Tue 20 OctStožec 14:01No data—
Mon 19 OctStožec 14:01No data—
Fri 16 OctStožec 14:01No data—
Thu 15 OctStožec 14:01No data—
Wed 14 OctStožec 14:01No data—
Tue 13 OctStožec 14:01No data—
Mon 12 OctStožec 14:01No data—
Fri 9 OctStožec 14:01No data—
Thu 8 OctStožec 14:01No data—
Wed 7 OctStožec 14:01No data—
Tue 6 OctStožec 14:01No data—
Mon 5 Oct— 14:140 min—
Fri 2 Oct— 14:160 min—
Thu 1 Oct— 14:160 min—
Wed 30 Sept— 14:150 min—
Tue 29 Sept— 14:13−1 min—
Fri 25 Sept— 14:140 min—
Thu 24 Sept— 14:150 min+2 min
Wed 23 Sept— 14:150 min—
Tue 22 Sept— 14:140 min—