Os 8453 8453 Milevsko – Tábor

View line Os 8453

Milevsko 07:09 → Tábor 07:42 Sat 0 h 33 min · 8 stops České dráhy, a.s.

It does not run today

Last recorded run: Saturday 31 October No data

Next service: Saturday 07:09 from Milevsko · Sat 7 Nov

Next departure 07:09 Saturday · Milevsko
On-time · 30 days
—
Too little data (0/5 runs with data)
RT coverage: 0 full · 0 partial · 5 no data
On-time · 90 days
89%
8/9 runs under 3 min
RT coverage: 9 full · 0 partial · 5 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
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

  • Sat 5 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 8
  • 3–10 min 11% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • 89% S n=9
  • — S n=0

Stops and timetable

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

Last 90 days, 9 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
07:09on time on time
07:13≈ on time ≈ on time
07:21 / 07:22≈ on time ≈ on time
07:25 / 07:26≈ on time ≈ on time
07:30≈ on time ≈ on time
07:32 / 07:33≈ on time ≈ on time
07:36≈ on time ≈ on time
07:42on time +1 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
Sat 31 OctTábor 07:43No data—
Wed 28 OctTábor 07:43No data—
Sat 24 OctTábor 07:43No data—
Sat 17 OctTábor 07:43No data—
Sat 10 OctTábor 07:43No data—
Sat 3 Oct— 07:570 min—
Sat 26 Sept— 07:56−1 min—
Sat 19 Sept— 07:570 min—
Sat 12 Sept— 07:580 min+1 min
Sat 5 Sept— 07:59+3 min+4 min
Sat 29 Aug— 07:570 min—
Sat 22 Aug— 07:560 min+1 min
Sat 15 Aug— 07:55−1 min+1 min
Sat 8 Aug— 07:570 min—