Os 8062 8062 České Budějovice – Protivín

View line Os 8062

České Budějovice 15:28 → Protivín 16:07 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 11 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Protivín at 16:08 No data

  1. České Budějovice15:28
  2. Hluboká nad Vltavou15:35
  3. Zliv15:42
  4. Dívčice15:49
  5. Číčenice15:57
  6. Milenovice16:00
  7. Protivín16:07

Next service: tomorrow 15:28 from České Budějovice · Thu 12 Nov

Next departure 15:28 tomorrow · České Budějovice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
78%
28/36 runs under 3 min
RT coverage: 36 full · 0 partial · 26 no data
Typical delay
0min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Protivín, 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 20 Aug Max en route +15 min · last fix heading to — +14 min
  • Thu 3 Sept Max en route +11 min · last fix heading to — +10 min
  • Tue 1 Sept Max en route +14 min · last fix heading to — +10 min
  • Thu 1 Oct Max en route +12 min · last fix heading to — +8 min
  • Fri 2 Oct Max en route +12 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 14% · 5
  • On time 64% · 23
  • 3–10 min 14% · 5
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 71% T n=7
  • 86% W n=7
  • 57% T n=7
  • 75% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 36 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
15:28on time on time
15:30≈ on time ≈ on time
15:35 / 15:37≈ on time ≈ +1 min
15:42 / 15:43≈ on time ≈ +3 min
15:46≈ on time ≈ +3 min
15:49 / 15:50≈ on time ≈ +4 min
15:53≈ on time ≈ +5 min
15:57 / 15:58≈ on time ≈ +6 min
16:00≈ on time ≈ +6 min
16:03≈ on time ≈ +7 min
16:07on time +8 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
Wed 11 NovProtivín 16:08No data—
Tue 10 NovProtivín 16:08No data—
Mon 9 NovProtivín 16:08No data—
Fri 6 NovProtivín 16:08No data—
Thu 5 NovProtivín 16:08No data—
Wed 4 NovProtivín 16:08No data—
Tue 3 NovProtivín 16:08No data—
Mon 2 NovProtivín 16:08No data—
Fri 30 OctProtivín 16:08No data—
Thu 29 OctProtivín 16:08No data—
Tue 27 OctProtivín 16:08No data—
Mon 26 OctProtivín 16:08No data—
Fri 23 OctProtivín 16:08No data—
Thu 22 OctProtivín 16:08No data—
Wed 21 OctProtivín 16:08No data—
Tue 20 OctProtivín 16:08No data—
Mon 19 OctProtivín 16:08No data—
Fri 16 OctProtivín 16:08No data—
Thu 15 OctProtivín 16:08No data—
Wed 14 OctProtivín 16:08No data—
Tue 13 OctProtivín 16:08No data—
Mon 12 OctProtivín 16:08No data—
Fri 9 OctProtivín 16:08No data—
Thu 8 OctProtivín 16:08No data—
Wed 7 OctProtivín 16:08No data—
Tue 6 OctProtivín 16:08No data—
Mon 5 Oct— 16:20−1 min+5 min
Fri 2 Oct— 16:28+7 min+12 min
Thu 1 Oct— 16:30+8 min+12 min
Wed 30 Sept— 16:220 min+3 min