Os 8432 8432 Tábor – Písek

View line Os 8432

Tábor 16:11 → Písek 17:31 Mon, Tue, Wed, Thu, Fri 1 h 20 min · 19 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Písek at 17:32 No data

  1. Tábor16:11
  2. Meziříčí16:22
  3. Sepekov16:39
  4. Branice16:52
  5. Červená nad Vltavou17:05
  6. Vrcovice17:20
  7. Písek17:31

Next service: Monday 16:11 from Tábor · Mon 9 Nov

Next departure 16:11 Monday · Tábor
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%
31/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
+1min
Median at arrival, 90 days
P90
+4min
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

  • Wed 16 Sept Max en route +21 min · last fix heading to — +13 min
  • Fri 18 Sept Max en route +16 min · last fix heading to — +12 min
  • Fri 4 Sept Max en route +13 min · last fix heading to — +12 min
  • Mon 17 Aug Max en route +6 min · last fix heading to — +6 min
  • Thu 1 Oct Max en route +6 min · last fix heading to — +4 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 78% · 31
  • 3–10 min 15% · 6
  • 10–30 min 8% · 3
  • 30+ min 0% · 0

On-time by weekday

  • 63% M n=8
  • 88% T n=8
  • 88% W n=8
  • 88% T n=8
  • 63% 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
16:11on time +2 min
16:16≈ on time ≈ +2 min
16:19 / 16:20≈ on time ≈ +2 min
16:22≈ on time ≈ +2 min
16:26 / 16:27≈ on time ≈ +2 min
16:30 / 16:32≈ on time ≈ +3 min
16:39≈ on time ≈ +4 min
16:43 / 16:45≈ on time ≈ +4 min
16:48≈ on time ≈ +4 min
16:52 / 16:55≈ +1 min ≈ +4 min
16:58≈ +1 min ≈ +4 min
17:02≈ +1 min ≈ +4 min
17:05 / 17:06≈ +1 min ≈ +4 min
17:11 / 17:12≈ +1 min ≈ +4 min
17:16 / 17:17≈ +1 min ≈ +4 min
17:20 / 17:21≈ +1 min ≈ +4 min
17:25≈ +1 min ≈ +4 min
17:28 / 17:29≈ +1 min ≈ +4 min
17:31+1 min +4 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 NovPísek 17:32No data—
Thu 5 NovPísek 17:32No data—
Wed 4 NovPísek 17:32No data—
Tue 3 NovPísek 17:32No data—
Mon 2 NovPísek 17:32No data—
Fri 30 OctPísek 17:32No data—
Thu 29 OctPísek 17:32No data—
Tue 27 OctPísek 17:32No data—
Mon 26 OctPísek 17:32No data—
Fri 23 OctPísek 17:33No data—
Thu 22 OctPísek 17:32No data—
Wed 21 OctPísek 17:32No data—
Tue 20 OctPísek 17:33No data—
Mon 19 OctPísek 17:32No data—
Fri 16 OctPísek 17:32No data—
Thu 15 OctPísek 17:32No data—
Wed 14 OctPísek 17:32No data—
Tue 13 OctPísek 17:32No data—
Mon 12 OctPísek 17:33No data—
Fri 9 OctPísek 17:32No data—
Thu 8 OctPísek 17:32No data—
Wed 7 OctPísek 17:32No data—
Tue 6 OctPísek 17:32No data—
Mon 5 OctPísek 17:32+1 min+2 min
Fri 2 Oct— 17:450 min+2 min
Thu 1 Oct— 17:49+4 min+6 min
Wed 30 Sept— 17:47+1 min+3 min
Tue 29 Sept— 17:450 min+3 min
Fri 25 Sept— 17:460 min+3 min
Thu 24 Sept— 17:450 min+2 min