Os 8426 8426 Tábor – Písek

View line Os 8426

Tábor 10:11 → Písek 11: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 11:32 No data

  1. Tábor10:11
  2. Meziříčí10:22
  3. Sepekov10:39
  4. Branice10:52
  5. Červená nad Vltavou11:05
  6. Vrcovice11:20
  7. Písek11:31

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

Next departure 10: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
93%
37/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
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

  • Tue 8 Sept Max en route +23 min · last fix heading to — +23 min
  • Tue 11 Aug Max en route +17 min · last fix heading to — +11 min
  • Wed 12 Aug Max en route +7 min · last fix heading to — +3 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 93% · 37
  • 3–10 min 3% · 1
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

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