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

View line Os 17520

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

✓ Today’s run finished

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

  1. Horažďovice předměstí17:11
  2. Žichovice17:26
  3. Hrádek u Sušice17:39
  4. Malonice17:54
  5. Běšiny18:05
  6. Luby u Klatov18:14
  7. Klatovy18:22

Next service: tomorrow 17:11 from Horažďovice předměstí · Mon 9 Nov

Next departure 17: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
15%
8/55 runs under 3 min
RT coverage: 55 full · 0 partial · 35 no data
Typical delay
+10min
Median at arrival, 90 days
P90
+20min
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

  • Fri 11 Sept Max en route +34 min · last fix heading to — +34 min
  • Sun 6 Sept Max en route +24 min · last fix heading to — +24 min
  • Fri 28 Aug Max en route +24 min · last fix heading to — +24 min
  • Sun 13 Sept Max en route +23 min · last fix heading to — +23 min
  • Wed 12 Aug Max en route +21 min · last fix heading to — +21 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 13% · 7
  • 3–10 min 33% · 18
  • 10–30 min 51% · 28
  • 30+ min 2% · 1

On-time by weekday

  • 0% M n=7
  • 25% T n=8
  • 0% W n=8
  • 13% T n=8
  • 13% F n=8
  • 38% S n=8
  • 13% S n=8

Stops and timetable

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

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