Os 8427 8427 Písek – Tábor

View line Os 8427

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

It does not run today

Last recorded run: Monday 16 November No data

Next service: tomorrow 10:18 from Písek · Wed 18 Nov

Next departure 10:18 tomorrow · Písek
On-time · 30 days
—
Too little data (0/20 runs with data)
RT coverage: 0 full · 0 partial · 20 no data
On-time · 90 days
81%
26/32 runs under 3 min
RT coverage: 32 full · 0 partial · 29 no data
Typical delay
0min
Median at arrival, 90 days
P90
+5min
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

  • Thu 1 Oct Max en route +8 min · last fix heading to — +8 min
  • Thu 24 Sept Max en route +9 min · last fix heading to — +6 min
  • Tue 25 Aug Max en route +10 min · last fix heading to — +6 min
  • Wed 23 Sept Max en route +5 min · last fix heading to — +5 min
  • Mon 14 Sept Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 26
  • 3–10 min 19% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 83% T n=6
  • 67% W n=6
  • 71% T n=7
  • 100% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

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