Os 18061 18061 Stožec – Volary

View line Os 18061

Stožec 07:20 → Volary 07:36 Mon, Tue, Wed, Thu, Fri 0 h 16 min · 4 stops GW Train Regio a.s.

It does not run today

Last recorded run: Monday 16 November No data

Next service: tomorrow 07:20 from Stožec · Wed 18 Nov

Next departure 07:20 tomorrow · Stožec
On-time · 30 days
—
Too little data (0/18 runs with data)
RT coverage: 0 full · 0 partial · 18 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 27 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 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
07:20on time on time
07:26 / 07:28≈ on time ≈ on time
07:31≈ on time ≈ on time
07:36on 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
Mon 16 NovVolary 07:37No data—
Fri 13 NovVolary 07:37No data—
Thu 12 NovVolary 07:37No data—
Wed 11 NovVolary 07:37No data—
Tue 10 NovVolary 07:37No data—
Mon 9 NovVolary 07:37No data—
Fri 6 NovVolary 07:37No data—
Thu 5 NovVolary 07:37No data—
Wed 4 NovVolary 07:37No data—
Tue 3 NovVolary 07:37No data—
Mon 2 NovVolary 07:37No data—
Tue 27 OctVolary 07:37No data—
Mon 26 OctVolary 07:37No data—
Fri 23 OctVolary 07:37No data—
Thu 22 OctVolary 07:37No data—
Wed 21 OctVolary 07:37No data—
Tue 20 OctVolary 07:37No data—
Mon 19 OctVolary 07:37No data—
Fri 16 OctVolary 07:37No data—
Thu 15 OctVolary 07:37No data—
Wed 14 OctVolary 07:37No data—
Tue 13 OctVolary 07:37No data—
Mon 12 OctVolary 07:37No data—
Fri 9 OctVolary 07:37No data—
Thu 8 OctVolary 07:37No data—
Wed 7 OctVolary 07:37No data—
Tue 6 OctVolary 07:37No data—
Mon 5 Oct— 07:50−1 min—
Fri 2 Oct— 07:50−1 min—
Thu 1 Oct— 07:510 min—