Sp 2073 2073 Strakonice – Tábor

View line Sp 2073

Strakonice 17:17 → Tábor 18:47 Mon, Tue, Wed, Thu, Fri 1 h 30 min · 25 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:17 from Strakonice · Thu 5 Nov

Next departure 17:17 today · Strakonice
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
46%
18/39 runs under 3 min
RT coverage: 39 full · 0 partial · 22 no data
Typical delay
+3min
Median at arrival, 90 days
P90
+8min
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

  • Fri 21 Aug Max en route +20 min · last fix heading to — +20 min
  • Thu 13 Aug Max en route +15 min · last fix heading to — +12 min
  • Fri 28 Aug Max en route +13 min · last fix heading to — +11 min
  • Wed 9 Sept Max en route +10 min · last fix heading to — +10 min
  • Thu 10 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 46% · 18
  • 3–10 min 44% · 17
  • 10–30 min 10% · 4
  • 30+ min 0% · 0

On-time by weekday

  • 57% M n=7
  • 63% T n=8
  • 63% W n=8
  • 13% T n=8
  • 38% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
17:17on time +6 min
17:20≈ on time ≈ +6 min
17:22 / 17:23≈ on time ≈ +6 min
17:25≈ +1 min ≈ +6 min
17:28 / 17:29≈ +1 min ≈ +7 min
17:33 / 17:34≈ +1 min ≈ +7 min
17:39 / 17:40≈ +1 min ≈ +7 min
17:42≈ +1 min ≈ +7 min
17:45 / 17:46≈ +1 min ≈ +7 min
17:49≈ +1 min ≈ +7 min
17:53 / 17:55≈ +2 min ≈ +7 min
17:59≈ +2 min ≈ +7 min
18:04≈ +2 min ≈ +7 min
18:07≈ +2 min ≈ +7 min
18:09≈ +2 min ≈ +7 min
18:11 / 18:12≈ +2 min ≈ +7 min
18:15≈ +2 min ≈ +7 min
18:18 / 18:19≈ +2 min ≈ +8 min
18:23≈ +2 min ≈ +8 min
18:31≈ +2 min ≈ +8 min
18:35≈ +3 min ≈ +8 min
18:38≈ +3 min ≈ +8 min
18:40≈ +3 min ≈ +8 min
18:42≈ +3 min ≈ +8 min
18:47+3 min +8 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
Wed 4 NovTábor 18:48No data—
Tue 3 NovTábor 18:48No data—
Mon 2 NovTábor 18:48No data—
Fri 30 OctTábor 18:48No data—
Thu 29 OctTábor 18:48No data—
Tue 27 OctTábor 18:49No data—
Mon 26 OctTábor 18:48No data—
Fri 23 OctTábor 18:49No data—
Thu 22 OctTábor 18:48No data—
Wed 21 OctTábor 18:48No data—
Tue 20 OctTábor 18:49No data—
Mon 19 OctTábor 18:48No data—
Fri 16 OctTábor 18:48No data—
Thu 15 OctTábor 18:48No data—
Wed 14 OctTábor 18:48No data—
Tue 13 OctTábor 18:48No data—
Mon 12 OctTábor 18:49No data—
Fri 9 OctTábor 18:48No data—
Thu 8 OctTábor 18:48No data—
Wed 7 OctTábor 18:48No data—
Tue 6 OctTábor 18:49No data—
Mon 5 OctTábor 18:48No data—
Fri 2 Oct— 19:03+1 min+1 min
Thu 1 Oct— 19:05+3 min+3 min
Wed 30 Sept— 19:04+2 min+3 min
Tue 29 Sept— 21:15+1 min+1 min
Fri 25 Sept— 19:020 min+2 min
Thu 24 Sept— 19:05+4 min+5 min
Wed 23 Sept— 19:020 min—
Tue 22 Sept— 19:020 min+5 min