Sp 1986 1986 České Budějovice – Písek

View line Sp 1986

České Budějovice 11:13 → Písek 12:00 Daily 0 h 47 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Písek at 11:59 No data

  1. České Budějovice11:13
  2. Hluboká nad Vltavou11:20
  3. Zbudov11:29
  4. Číčenice11:38
  5. Protivín zastávka11:43
  6. Heřmaň11:53
  7. Písek12:00

Next service: tomorrow 11:13 from České Budějovice · Sun 8 Nov

Next departure 11:13 tomorrow · České Budějovice
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
39%
22/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+10min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Písek, in minutes. One bar per run.

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

Worst days

  • Sat 3 Oct Max en route +15 min · last fix heading to — +15 min
  • Sat 19 Sept Max en route +15 min · last fix heading to — +13 min
  • Tue 29 Sept Max en route +12 min · last fix heading to — +12 min
  • Fri 4 Sept Max en route +12 min · last fix heading to — +12 min
  • Fri 11 Sept Max en route +13 min · last fix heading to — +11 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 39% · 22
  • 3–10 min 49% · 28
  • 10–30 min 12% · 7
  • 30+ min 0% · 0

On-time by weekday

  • 44% M n=9
  • 50% T n=8
  • 38% W n=8
  • 13% T n=8
  • 50% F n=8
  • 25% S n=8
  • 50% S n=8

Stops and timetable

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

Last 90 days, 57 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:13on time +4 min
11:15≈ on time ≈ +4 min
11:20 / 11:21≈ +1 min ≈ +5 min
11:25 / 11:26≈ +1 min ≈ +5 min
11:29≈ +1 min ≈ +5 min
11:31 / 11:32≈ +2 min ≈ +5 min
11:35≈ +2 min ≈ +6 min
11:38 / 11:39≈ +2 min ≈ +6 min
11:41≈ +2 min ≈ +6 min
11:43≈ +2 min ≈ +6 min
11:45 / 11:46≈ +2 min ≈ +7 min
11:53≈ +3 min ≈ +9 min
11:55 / 11:56≈ +3 min ≈ +9 min
12:00+3 min +10 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
Sat 7 NovPísek 11:59No data—
Fri 6 NovPísek 11:59No data—
Thu 5 NovPísek 11:59No data—
Wed 4 NovPísek 11:59No data—
Tue 3 NovPísek 11:59No data—
Mon 2 NovPísek 11:59No data—
Sun 1 NovPísek 12:01No data—
Sat 31 OctPísek 12:01No data—
Fri 30 OctPísek 12:01No data—
Thu 29 OctPísek 12:01No data—
Wed 28 OctPísek 12:01No data—
Tue 27 OctPísek 12:01No data—
Mon 26 OctPísek 12:01No data—
Sun 25 OctPísek 12:01No data—
Sat 24 OctPísek 12:01No data—
Fri 23 OctPísek 12:01No data—
Thu 22 OctPísek 12:01No data—
Wed 21 OctPísek 12:01No data—
Tue 20 OctPísek 12:01No data—
Mon 19 OctPísek 12:01No data—
Sun 18 OctPísek 12:01No data—
Sat 17 OctPísek 12:01No data—
Fri 16 OctPísek 12:01No data—
Thu 15 OctPísek 12:01No data—
Wed 14 OctPísek 12:01No data—
Tue 13 OctPísek 12:01No data—
Mon 12 OctPísek 12:01No data—
Sun 11 OctPísek 12:01No data—
Sat 10 OctPísek 12:01No data—
Fri 9 OctPísek 12:01No data—