Os 8423 8423 Písek – Tábor

View line Os 8423

Písek 05:57 → Tábor 07:26 Mon, Tue, Wed, Thu, Fri 1 h 29 min · 19 stops České dráhy, a.s.

✓ Today’s run finished

Today, last fix heading to Tábor at 07:27 No data

  1. Písek05:57
  2. Vrcovice06:09
  3. Červená nad Vltavou06:25
  4. Branice06:45
  5. Sepekov06:57
  6. Meziříčí07:14
  7. Tábor07:26

Next service: Monday 05:57 from Písek · Mon 9 Nov

Next departure 05:57 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
+6min
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

  • Wed 23 Sept Max en route +40 min · last fix heading to — +29 min
  • Fri 18 Sept Max en route +28 min · last fix heading to — +24 min
  • Thu 1 Oct Max en route +9 min · last fix heading to — +9 min
  • Wed 9 Sept Max en route +7 min · last fix heading to — +7 min
  • Tue 8 Sept Max en route +7 min · last fix heading to — +6 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 30% · 12
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=8
  • 75% T n=8
  • 63% W n=8
  • 63% T n=8
  • 75% 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
05:57+1 min +3 min
05:59≈ +1 min ≈ +3 min
06:02 / 06:05≈ +1 min ≈ +3 min
06:09 / 06:10≈ +1 min ≈ +3 min
06:13 / 06:14≈ +1 min ≈ +3 min
06:18 / 06:19≈ +1 min ≈ +3 min
06:25 / 06:34≈ +2 min ≈ +3 min
06:38≈ +2 min ≈ +4 min
06:42≈ +2 min ≈ +4 min
06:45≈ +2 min ≈ +4 min
06:49≈ +2 min ≈ +4 min
06:53 / 06:54≈ +2 min ≈ +5 min
06:57 / 06:58≈ +2 min ≈ +5 min
07:05 / 07:06≈ +2 min ≈ +5 min
07:10≈ +2 min ≈ +5 min
07:14 / 07:15≈ +2 min ≈ +6 min
07:17≈ +2 min ≈ +6 min
07:20 / 07:21≈ +2 min ≈ +6 min
07:26+2 min +6 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 07:27No data—
Thu 5 NovTábor 07:27No data—
Wed 4 NovTábor 07:27No data—
Tue 3 NovTábor 07:27No data—
Mon 2 NovTábor 07:27No data—
Fri 30 OctTábor 07:27No data—
Thu 29 OctTábor 07:27No data—
Tue 27 OctTábor 07:27No data—
Mon 26 OctTábor 07:27No data—
Fri 23 OctTábor 07:27No data—
Thu 22 OctTábor 07:27No data—
Wed 21 OctTábor 07:27No data—
Tue 20 OctTábor 07:27No data—
Mon 19 OctTábor 07:27No data—
Fri 16 OctTábor 07:27No data—
Thu 15 OctTábor 07:27No data—
Wed 14 OctTábor 07:27No data—
Tue 13 OctTábor 07:27No data—
Mon 12 OctTábor 07:27No data—
Fri 9 OctTábor 07:27No data—
Thu 8 OctTábor 07:28No data—
Wed 7 OctTábor 07:27No data—
Tue 6 OctTábor 07:27No data—
Mon 5 Oct— 07:42+1 min+4 min
Fri 2 Oct— 07:43+2 min+2 min
Thu 1 Oct— 07:50+9 min+9 min
Wed 30 Sept— 07:43+3 min+3 min
Tue 29 Sept— 07:42+2 min+4 min
Fri 25 Sept— 07:42+2 min+3 min
Thu 24 Sept— 07:400 min+3 min