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

View line Sp 1987

Písek 06:53 → České Budějovice 07:44 Tue, Sat, Sun 0 h 51 min · 14 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to České Budějovice at 07:44 No data

  1. Písek06:53
  2. Heřmaň07:00
  3. Protivín zastávka07:11
  4. Záblatíčko07:20
  5. Zbudov07:26
  6. Hluboká nad Vltavou07:35
  7. České Budějovice07:44

Next service: tomorrow 06:53 from Písek · Sun 15 Nov

Next departure 06:53 tomorrow · Písek
On-time · 30 days
—
Too little data (0/10 runs with data)
RT coverage: 0 full · 0 partial · 10 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 12 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at České Budějovice, 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 5 Sept Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 86% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 15 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:53on time +2 min
06:57 / 06:58≈ on time ≈ +2 min
07:00≈ on time ≈ +2 min
07:07 / 07:09≈ +1 min ≈ +2 min
07:11≈ +1 min ≈ +2 min
07:13≈ +1 min ≈ +2 min
07:16 / 07:17≈ +1 min ≈ +2 min
07:20≈ +1 min ≈ +2 min
07:23 / 07:24≈ +1 min ≈ +2 min
07:26≈ +1 min ≈ +2 min
07:29 / 07:30≈ +1 min ≈ +2 min
07:35 / 07:36≈ +2 min ≈ +2 min
07:42≈ +2 min ≈ +2 min
07:44+2 min +2 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 14 NovČeské Budějovice 07:44No data—
Sun 8 NovČeské Budějovice 07:44No data—
Sat 7 NovČeské Budějovice 07:44No data—
Sun 1 NovČeské Budějovice 07:45No data—
Sat 31 OctČeské Budějovice 07:45No data—
Wed 28 OctČeské Budějovice 07:45No data—
Sun 25 OctČeské Budějovice 07:45No data—
Sat 24 OctČeské Budějovice 07:45No data—
Sun 18 OctČeské Budějovice 07:45No data—
Sat 17 OctČeské Budějovice 07:45No data—
Sun 11 OctČeské Budějovice 07:45No data—
Sat 10 OctČeské Budějovice 07:45No data—
Sun 4 Oct— 08:01+2 min+2 min
Sat 3 Oct— 08:00+1 min+1 min
Mon 28 Sept— 08:00+1 min+1 min
Sun 27 Sept— 08:01+2 min+2 min
Sat 26 Sept— 08:01+2 min+2 min
Sun 20 Sept— 07:590 min—
Sat 19 Sept— 07:590 min—
Sun 13 Sept— 07:59+1 min+1 min
Sat 12 Sept— 08:01+2 min+2 min
Sun 6 Sept— 07:590 min—
Sat 5 Sept— 08:02+4 min+4 min
Sun 30 Aug— 08:01+2 min+2 min
Sat 29 Aug— 08:01+2 min+2 min
Sun 23 Aug— 08:00+2 min+2 min
Sat 22 Aug— 08:01+2 min+2 min