Os 18060 18060 Volary – Stožec

View line Os 18060

Volary 05:55 → Stožec 06:09 Mon, Tue, Wed, Thu, Fri 0 h 14 min · 4 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 05:55 from Volary · Mon 9 Nov

Next departure 05:55 today · Volary
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%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 23 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 38 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
05:55on time on time
05:59≈ on time ≈ on time
06:02 / 06:03≈ on time ≈ on time
06:09on 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 06:09No data—
Thu 5 NovStožec 06:09No data—
Wed 4 NovStožec 06:09No data—
Tue 3 NovStožec 06:10No data—
Mon 2 NovStožec 06:09No data—
Fri 30 OctStožec 06:10No data—
Thu 29 OctStožec 06:10No data—
Tue 27 OctStožec 06:10No data—
Mon 26 OctStožec 06:10No data—
Fri 23 OctStožec 06:10No data—
Thu 22 OctStožec 06:10No data—
Wed 21 OctStožec 06:10No data—
Tue 20 OctStožec 06:10No data—
Mon 19 OctStožec 06:10No data—
Fri 16 OctStožec 06:10No data—
Thu 15 OctStožec 06:10No data—
Wed 14 OctStožec 06:10No data—
Tue 13 OctStožec 06:10No data—
Mon 12 OctStožec 06:10No data—
Fri 9 OctStožec 06:10No data—
Thu 8 OctStožec 06:10No data—
Wed 7 OctStožec 06:10No data—
Tue 6 OctStožec 06:11No data—
Mon 5 Oct— 06:230 min—
Fri 2 Oct— 06:240 min—
Thu 1 Oct— 06:240 min—
Wed 30 Sept— 06:240 min—
Tue 29 Sept— 06:230 min—
Fri 25 Sept— 07:030 min—
Thu 24 Sept— 06:230 min—