Os 17512 17512 Horažďovice předměstí – Klatovy

View line Os 17512

Horažďovice předměstí 13:11 → Klatovy 14:22 Daily 1 h 11 min · 16 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Klatovy at 14:23 No data

  1. Horažďovice předměstí13:11
  2. Žichovice13:26
  3. Hrádek u Sušice13:39
  4. Malonice13:54
  5. Běšiny14:05
  6. Luby u Klatov14:14
  7. Klatovy14:22

Next service: tomorrow 13:11 from Horažďovice předměstí · Sun 8 Nov

Next departure 13:11 tomorrow · Horažďovice předměstí
On-time · 30 days
—
Too little data (0/30 runs with data)
RT coverage: 0 full · 0 partial · 30 no data
On-time · 90 days
23%
13/57 runs under 3 min
RT coverage: 57 full · 0 partial · 33 no data
Typical delay
+7min
Median at arrival, 90 days
P90
+17min
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

  • Thu 13 Aug Max en route +31 min · last fix heading to — +27 min
  • Sun 6 Sept Max en route +23 min · last fix heading to — +23 min
  • Thu 27 Aug Max en route +23 min · last fix heading to — +23 min
  • Thu 17 Sept Max en route +21 min · last fix heading to — +21 min
  • Sat 5 Sept Max en route +21 min · last fix heading to — +21 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 21% · 12
  • 3–10 min 46% · 26
  • 10–30 min 32% · 18
  • 30+ min 0% · 0

On-time by weekday

  • 33% M n=9
  • 13% T n=8
  • 25% W n=8
  • 25% T n=8
  • 13% F n=8
  • 25% S n=8
  • 25% S n=8

Stops and timetable

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

Last 90 days, 57 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:11+3 min +12 min
13:14 / 13:15≈ +3 min ≈ +12 min
13:20 / 13:21≈ +3 min ≈ +12 min
13:26 / 13:27≈ +3 min ≈ +12 min
13:33 / 13:34≈ +3 min ≈ +12 min
13:39 / 13:40≈ +3 min ≈ +12 min
13:43≈ +4 min ≈ +13 min
13:47 / 13:48≈ +4 min ≈ +13 min
13:54≈ +5 min ≈ +13 min
13:58 / 13:59≈ +5 min ≈ +14 min
14:05≈ +6 min ≈ +16 min
14:08≈ +6 min ≈ +16 min
14:12≈ +6 min ≈ +17 min
14:14≈ +6 min ≈ +17 min
14:18≈ +7 min ≈ +17 min
14:22+7 min +17 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 7 NovKlatovy 14:23No data—
Fri 6 NovKlatovy 14:23No data—
Thu 5 NovKlatovy 14:23No data—
Wed 4 NovKlatovy 14:24No data—
Tue 3 NovKlatovy 14:23No data—
Mon 2 NovKlatovy 14:23No data—
Sun 1 NovKlatovy 14:23No data—
Sat 31 OctKlatovy 14:23No data—
Fri 30 OctKlatovy 14:23No data—
Thu 29 OctKlatovy 14:23No data—
Wed 28 OctKlatovy 14:23No data—
Tue 27 OctKlatovy 14:23No data—
Mon 26 OctKlatovy 14:23No data—
Sun 25 OctKlatovy 14:23No data—
Sat 24 OctKlatovy 14:23No data—
Fri 23 OctKlatovy 14:23No data—
Thu 22 OctKlatovy 14:23No data—
Wed 21 OctKlatovy 14:23No data—
Tue 20 OctKlatovy 14:23No data—
Mon 19 OctKlatovy 14:23No data—
Sun 18 OctKlatovy 14:24No data—
Sat 17 OctKlatovy 14:23No data—
Fri 16 OctKlatovy 14:23No data—
Thu 15 OctKlatovy 14:23No data—
Wed 14 OctKlatovy 14:23No data—
Tue 13 OctKlatovy 14:23No data—
Mon 12 OctKlatovy 14:23No data—
Sun 11 OctKlatovy 14:23No data—
Sat 10 OctKlatovy 14:23No data—
Fri 9 OctKlatovy 14:23No data—