Os 18003 18003 Volary – Číčenice

View line Os 18003

Volary 06:40 → Číčenice 08:14 Daily 1 h 34 min · 17 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Číčenice at 08:14 No data

  1. Volary06:40
  2. Skříněřov07:02
  3. Chroboly07:10
  4. Prachatice07:24
  5. Blanice07:49
  6. Svinětice08:00
  7. Číčenice08:14

Next service: tomorrow 06:40 from Volary · Mon 9 Nov

Next departure 06:40 tomorrow · Volary
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
86%
48/56 runs under 3 min
RT coverage: 56 full · 0 partial · 34 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+3min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Číčenice, in minutes. One bar per run.

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

Worst days

  • Thu 10 Sept Max en route +11 min · last fix heading to — +10 min
  • Mon 5 Oct Max en route +5 min · last fix heading to — +4 min
  • Thu 20 Aug Max en route +5 min · last fix heading to — +4 min
  • Wed 12 Aug Max en route +7 min · last fix heading to — +4 min
  • Sat 3 Oct Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 84% · 47
  • 3–10 min 13% · 7
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 56 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:40on time on time
06:52≈ on time ≈ on time
06:54 / 06:57≈ on time ≈ on time
07:02≈ on time ≈ +1 min
07:07≈ on time ≈ +1 min
07:10 / 07:11≈ on time ≈ +1 min
07:15≈ on time ≈ +1 min
07:21≈ on time ≈ +1 min
07:24 / 07:33≈ on time ≈ +1 min
07:38≈ +1 min ≈ +2 min
07:45 / 07:46≈ +1 min ≈ +2 min
07:49≈ +1 min ≈ +2 min
07:54 / 07:57≈ +1 min ≈ +2 min
08:00≈ +1 min ≈ +3 min
08:04≈ +1 min ≈ +3 min
08:07 / 08:08≈ +1 min ≈ +3 min
08:14+1 min +3 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
Sun 8 NovČíčenice 08:14No data—
Sat 7 NovČíčenice 08:14No data—
Fri 6 NovČíčenice 08:14No data—
Thu 5 NovČíčenice 08:14No data—
Wed 4 NovČíčenice 08:14No data—
Tue 3 NovČíčenice 08:14No data—
Mon 2 NovČíčenice 08:14No data—
Sun 1 NovČíčenice 08:15No data—
Sat 31 OctČíčenice 08:15No data—
Fri 30 OctČíčenice 08:15No data—
Thu 29 OctČíčenice 08:15No data—
Wed 28 OctČíčenice 08:15No data—
Tue 27 OctČíčenice 08:15No data—
Mon 26 OctČíčenice 08:15No data—
Sun 25 OctČíčenice 08:15No data—
Sat 24 OctČíčenice 08:15No data—
Fri 23 OctČíčenice 08:15No data—
Thu 22 OctČíčenice 08:16No data—
Wed 21 OctČíčenice 08:15No data—
Tue 20 OctČíčenice 08:15No data—
Mon 19 OctČíčenice 08:15No data—
Sun 18 OctČíčenice 08:15No data—
Sat 17 OctČíčenice 08:15No data—
Fri 16 OctČíčenice 08:15No data—
Thu 15 OctČíčenice 08:15No data—
Wed 14 OctČíčenice 08:15No data—
Tue 13 OctČíčenice 08:15No data—
Mon 12 OctČíčenice 08:15No data—
Sun 11 OctČíčenice 08:15No data—
Sat 10 OctČíčenice 08:15No data—