Os 18021 18021 Prachatice – Číčenice

View line Os 18021

Prachatice 04:32 → Číčenice 05:12 Mon, Tue, Wed, Thu, Fri 0 h 40 min · 9 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Číčenice at 05:13 No data

  1. Prachatice04:32
  2. Husinec04:37
  3. Blanice04:48
  4. Bavorov04:54
  5. Svinětice04:58
  6. Vodňany05:05
  7. Číčenice05:12

Next service: tomorrow 04:32 from Prachatice · Tue 10 Nov

Next departure 04:32 tomorrow · Prachatice
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 24 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 Číčenice, 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 3% · 1
  • On time 97% · 37
  • 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 (9 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
04:32on time on time
04:37≈ on time ≈ on time
04:44 / 04:45≈ on time ≈ on time
04:48≈ on time ≈ on time
04:54 / 04:55≈ on time ≈ on time
04:58≈ on time ≈ on time
05:02≈ on time ≈ on time
05:05 / 05:06≈ on time ≈ on time
05:12on 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 9 NovČíčenice 05:13No data—
Fri 6 NovČíčenice 05:13No data—
Thu 5 NovČíčenice 05:13No data—
Wed 4 NovČíčenice 05:13No data—
Tue 3 NovČíčenice 05:14No data—
Mon 2 NovČíčenice 05:13No data—
Fri 30 OctČíčenice 05:13No data—
Thu 29 OctČíčenice 05:13No data—
Tue 27 OctČíčenice 05:13No data—
Mon 26 OctČíčenice 05:13No data—
Fri 23 OctČíčenice 05:13No data—
Thu 22 OctČíčenice 05:13No data—
Wed 21 OctČíčenice 05:13No data—
Tue 20 OctČíčenice 05:13No data—
Mon 19 OctČíčenice 05:13No data—
Fri 16 OctČíčenice 05:13No data—
Thu 15 OctČíčenice 05:13No data—
Wed 14 OctČíčenice 05:13No data—
Tue 13 OctČíčenice 05:13No data—
Mon 12 OctČíčenice 05:13No data—
Fri 9 OctČíčenice 05:13No data—
Thu 8 OctČíčenice 05:13No data—
Wed 7 OctČíčenice 05:13No data—
Tue 6 OctČíčenice 05:13No data—
Mon 5 Oct— 05:270 min+2 min
Fri 2 Oct— 05:260 min+1 min
Thu 1 Oct— 05:25−1 min+1 min
Wed 30 Sept— 05:260 min—
Tue 29 Sept— 05:27+1 min+2 min
Fri 25 Sept— 05:270 min+2 min