Os 17514 17514 Strakonice – Klatovy

View line Os 17514

Strakonice 13:55 → Klatovy 15:27 Mon, Tue, Wed, Thu, Fri 1 h 32 min · 21 stops GW Train Regio a.s.

It has not run yet today

Last recorded run: Friday 13 November No data

Next service: today 13:55 from Strakonice · Mon 16 Nov

Next departure 13:55 today · Strakonice
On-time · 30 days
—
Too little data (0/19 runs with data)
RT coverage: 0 full · 0 partial · 19 no data
On-time · 90 days
12%
4/33 runs under 3 min
RT coverage: 33 full · 0 partial · 28 no data
Typical delay
+12min
Median at arrival, 90 days
P90
+19min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Klatovy, 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 16 Sept Max en route +23 min · last fix heading to — +23 min
  • Wed 26 Aug Max en route +22 min · last fix heading to — +22 min
  • Tue 25 Aug Max en route +22 min · last fix heading to — +20 min
  • Mon 24 Aug Max en route +19 min · last fix heading to — +19 min
  • Wed 9 Sept Max en route +18 min · last fix heading to — +18 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 12% · 4
  • 3–10 min 24% · 8
  • 10–30 min 64% · 21
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=6
  • 33% T n=6
  • 14% W n=7
  • 14% T n=7
  • 0% F n=7
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 33 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
13:55+2 min +6 min
13:59≈ +2 min ≈ +7 min
14:02 / 14:03≈ +2 min ≈ +7 min
14:05≈ +3 min ≈ +7 min
14:08 / 14:09≈ +3 min ≈ +8 min
14:13 / 14:15≈ +4 min ≈ +9 min
14:18 / 14:19≈ +4 min ≈ +9 min
14:24 / 14:25≈ +5 min ≈ +9 min
14:30 / 14:32≈ +6 min ≈ +10 min
14:38 / 14:40≈ +7 min ≈ +11 min
14:45 / 14:46≈ +8 min ≈ +12 min
14:48≈ +8 min ≈ +12 min
14:53≈ +8 min ≈ +13 min
14:59≈ +9 min ≈ +14 min
15:04≈ +10 min ≈ +15 min
15:11≈ +11 min ≈ +16 min
15:14≈ +11 min ≈ +17 min
15:18≈ +11 min ≈ +17 min
15:20≈ +11 min ≈ +18 min
15:23≈ +12 min ≈ +18 min
15:27+12 min +19 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 13 NovKlatovy 15:28No data—
Thu 12 NovKlatovy 15:28No data—
Wed 11 NovKlatovy 15:28No data—
Tue 10 NovKlatovy 15:28No data—
Mon 9 NovKlatovy 15:28No data—
Fri 6 NovKlatovy 15:28No data—
Thu 5 NovKlatovy 15:28No data—
Wed 4 NovKlatovy 15:29No data—
Tue 3 NovKlatovy 15:28No data—
Mon 2 NovKlatovy 15:28No data—
Fri 30 OctKlatovy 15:28No data—
Thu 29 OctKlatovy 15:28No data—
Tue 27 OctKlatovy 15:28No data—
Mon 26 OctKlatovy 15:28No data—
Fri 23 OctKlatovy 15:28No data—
Thu 22 OctKlatovy 15:28No data—
Wed 21 OctKlatovy 15:28No data—
Tue 20 OctKlatovy 15:28No data—
Mon 19 OctKlatovy 15:28No data—
Fri 16 OctKlatovy 15:28No data—
Thu 15 OctKlatovy 15:28No data—
Wed 14 OctKlatovy 15:28No data—
Tue 13 OctKlatovy 15:28No data—
Mon 12 OctKlatovy 15:28No data—
Fri 9 OctKlatovy 15:28No data—
Thu 8 OctKlatovy 15:28No data—
Wed 7 OctKlatovy 15:28No data—
Tue 6 OctKlatovy 15:28No data—
Mon 5 Oct— 15:35+3 min+6 min
Fri 2 Oct— 15:42+10 min+10 min