Os 8425 8425 Písek – Tábor

View line Os 8425

Písek 08:18 → Tábor 09:39 Mon, Tue, Wed, Thu, Fri 1 h 21 min · 19 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Tábor at 09:39 No data

  1. Písek08:18
  2. Vrcovice08:28
  3. Červená nad Vltavou08:42
  4. Branice08:53
  5. Sepekov09:07
  6. Meziříčí09:26
  7. Tábor09:39

Next service: Monday 08:18 from Písek · Mon 9 Nov

Next departure 08:18 Monday · Písek
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
65%
26/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
+2min
Median at arrival, 90 days
P90
+8min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Tábor, in minutes. One bar per run.

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

Worst days

  • Tue 11 Aug Max en route +52 min · last fix heading to — +45 min
  • Thu 10 Sept Max en route +15 min · last fix heading to — +15 min
  • Mon 5 Oct Max en route +10 min · last fix heading to — +10 min
  • Thu 13 Aug Max en route +10 min · last fix heading to — +9 min
  • Thu 1 Oct Max en route +10 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 65% · 26
  • 3–10 min 28% · 11
  • 10–30 min 5% · 2
  • 30+ min 3% · 1

On-time by weekday

  • 63% M n=8
  • 50% T n=8
  • 88% W n=8
  • 38% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
08:18on time +1 min
08:20≈ on time ≈ +1 min
08:23 / 08:24≈ on time ≈ +1 min
08:28≈ on time ≈ +1 min
08:32≈ +1 min ≈ +1 min
08:37≈ +1 min ≈ +2 min
08:42 / 08:43≈ +1 min ≈ +2 min
08:46≈ +1 min ≈ +3 min
08:50≈ +1 min ≈ +3 min
08:53 / 08:54≈ +1 min ≈ +4 min
08:58≈ +1 min ≈ +4 min
09:02 / 09:04≈ +1 min ≈ +4 min
09:07 / 09:08≈ +1 min ≈ +5 min
09:15 / 09:18≈ +1 min ≈ +6 min
09:22≈ +2 min ≈ +6 min
09:26 / 09:27≈ +2 min ≈ +7 min
09:29 / 09:30≈ +2 min ≈ +7 min
09:33≈ +2 min ≈ +8 min
09:39+2 min +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
Fri 6 NovTábor 09:39No data—
Thu 5 NovTábor 09:39No data—
Wed 4 NovTábor 09:39No data—
Tue 3 NovTábor 09:39No data—
Mon 2 NovTábor 09:39No data—
Fri 30 OctTábor 09:40No data—
Thu 29 OctTábor 09:40No data—
Tue 27 OctTábor 09:41No data—
Mon 26 OctTábor 09:40No data—
Fri 23 OctTábor 09:41No data—
Thu 22 OctTábor 09:41No data—
Wed 21 OctTábor 09:40No data—
Tue 20 OctTábor 09:40No data—
Mon 19 OctTábor 09:40No data—
Fri 16 OctTábor 09:40No data—
Thu 15 OctTábor 09:40No data—
Wed 14 OctTábor 09:40No data—
Tue 13 OctTábor 09:40No data—
Mon 12 OctTábor 09:40No data—
Fri 9 OctTábor 09:40No data—
Thu 8 OctTábor 09:40No data—
Wed 7 OctTábor 09:40No data—
Tue 6 OctTábor 09:40No data—
Mon 5 Oct— 10:04+10 min+10 min
Fri 2 Oct— 09:55+1 min+5 min
Thu 1 Oct— 10:02+8 min+10 min
Wed 30 Sept— 09:530 min+2 min
Tue 29 Sept— 09:540 min+2 min
Fri 25 Sept— 09:57+3 min+5 min
Thu 24 Sept— 09:57+3 min+9 min