Os 17571 17571 Domažlice – Klatovy

View line Os 17571

Domažlice 16:38 → Klatovy 17:28 Mon, Tue, Wed, Thu, Fri 0 h 50 min · 14 stops GW Train Regio a.s.

✓ Today’s run finished

Today, last fix heading to Klatovy at 17:29 No data

  1. Domažlice16:38
  2. Kout na Šumavě16:47
  3. Kdyně16:53
  4. Loučim17:04
  5. Úborsko17:14
  6. Janovice nad Úhlavou17:20
  7. Klatovy17:28

Next service: Monday 16:38 from Domažlice · Mon 9 Nov

Next departure 16:38 Monday · Domažlice
On-time · 30 days
—
Too little data (0/21 runs with data)
RT coverage: 0 full · 0 partial · 21 no data
On-time · 90 days
85%
34/40 runs under 3 min
RT coverage: 40 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
P90
+3min
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

  • Mon 10 Aug Max en route +11 min · last fix heading to — +9 min
  • Wed 9 Sept Max en route +10 min · last fix heading to — +6 min
  • Fri 4 Sept Max en route +12 min · last fix heading to — +6 min
  • Thu 17 Sept Max en route +11 min · last fix heading to — +3 min
  • Mon 14 Sept Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 34
  • 3–10 min 15% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=8
  • 100% T n=8
  • 88% W n=8
  • 75% T n=8
  • 88% F n=8
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 40 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
16:38+2 min +8 min
16:43≈ +2 min ≈ +7 min
16:47≈ +2 min ≈ +6 min
16:49≈ +2 min ≈ +6 min
16:53 / 16:54≈ +2 min ≈ +6 min
16:59≈ +2 min ≈ +5 min
17:01≈ +2 min ≈ +5 min
17:04≈ +1 min ≈ +5 min
17:08 / 17:09≈ +1 min ≈ +5 min
17:14≈ +1 min ≈ +4 min
17:16≈ +1 min ≈ +4 min
17:20 / 17:21≈ on time ≈ +4 min
17:24≈ on time ≈ +3 min
17:28on time +3 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 6 NovKlatovy 17:29No data—
Thu 5 NovKlatovy 17:29No data—
Wed 4 NovKlatovy 17:29No data—
Tue 3 NovKlatovy 17:29No data—
Mon 2 NovKlatovy 17:29No data—
Fri 30 OctKlatovy 17:29No data—
Thu 29 OctKlatovy 17:29No data—
Tue 27 OctKlatovy 17:29No data—
Mon 26 OctKlatovy 17:29No data—
Fri 23 OctKlatovy 17:30No data—
Thu 22 OctKlatovy 17:29No data—
Wed 21 OctKlatovy 17:29No data—
Tue 20 OctKlatovy 17:30No data—
Mon 19 OctKlatovy 17:29No data—
Fri 16 OctKlatovy 17:29No data—
Thu 15 OctKlatovy 17:29No data—
Wed 14 OctKlatovy 17:29No data—
Tue 13 OctKlatovy 17:29No data—
Mon 12 OctKlatovy 17:30No data—
Fri 9 OctKlatovy 17:29No data—
Thu 8 OctKlatovy 17:29No data—
Wed 7 OctKlatovy 17:29No data—
Tue 6 OctKlatovy 17:29No data—
Mon 5 OctKlatovy 17:270 min—
Fri 2 Oct— 17:420 min+9 min
Thu 1 Oct— 17:44+2 min+6 min
Wed 30 Sept— 17:430 min+3 min
Tue 29 Sept— 17:420 min—
Fri 25 Sept— 17:440 min+7 min
Thu 24 Sept— 17:41−1 min+6 min