Os 18063 18063 Černý Kříž – Volary

View line Os 18063

Černý Kříž 11:32 → Volary 11:40 Sat, Sun 0 h 08 min · 3 stops GW Train Regio a.s.

It does not run today

Last recorded run: Sunday 1 November No data

Next service: Saturday 11:32 from Černý Kříž · Sat 7 Nov

Next departure 11:32 Saturday · Černý Kříž
On-time · 30 days
—
Too little data (0/12 runs with data)
RT coverage: 0 full · 0 partial · 12 no data
On-time · 90 days
97%
57/59 runs under 3 min
RT coverage: 59 full · 0 partial · 13 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

Worst days

  • Fri 14 Aug Max en route +9 min · last fix heading to — +8 min
  • Wed 12 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 57
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 59 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
11:32on time +1 min
11:35≈ on time ≈ +1 min
11:40on 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
Sun 1 NovVolary 11:41No data—
Sat 31 OctVolary 11:41No data—
Wed 28 OctVolary 11:41No data—
Sun 25 OctVolary 11:41No data—
Sat 24 OctVolary 11:42No data—
Sun 18 OctVolary 11:41No data—
Sat 17 OctVolary 11:41No data—
Sun 11 OctVolary 11:41No data—
Sat 10 OctVolary 11:41No data—
Fri 9 OctVolary 11:41No data—
Thu 8 OctVolary 11:41No data—
Wed 7 OctVolary 11:41No data—
Tue 6 OctVolary 11:41No data—
Mon 5 Oct— 11:540 min—
Sun 4 Oct— 11:53−1 min—
Sat 3 Oct— 11:540 min—
Fri 2 Oct— 11:550 min—
Thu 1 Oct— 11:550 min—
Wed 30 Sept— 11:540 min—
Tue 29 Sept— 11:540 min—
Mon 28 Sept— 11:550 min—
Sun 27 Sept— 11:540 min—
Sat 26 Sept— 11:560 min—
Fri 25 Sept— 11:53−1 min—
Thu 24 Sept— 11:550 min—
Wed 23 Sept— 11:550 min—
Tue 22 Sept— 11:550 min—
Mon 21 Sept— 11:54−1 min—
Sun 20 Sept— 11:53−1 min—
Sat 19 Sept— 11:54−1 min—