Os 17648 17648 Kadaň-Prunéřov – Kadaň

View line Os 17648

Kadaň-Prunéřov 15:16 → Kadaň 15:24 Mon, Tue, Wed, Thu, Fri 0 h 08 min · 3 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 15:16 from Kadaň-Prunéřov · Fri 6 Nov

Next departure 15:16 today · Kadaň-Prunéřov
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
93%
37/40 runs under 3 min
RT coverage: 40 full · 0 partial · 22 no data
Typical delay
0min
Median at arrival, 90 days
P90
+2min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Kadaň, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 18 Aug Max en route +20 min · last fix heading to — +19 min
  • Thu 10 Sept Max en route +9 min · last fix heading to — +9 min
  • Fri 4 Sept Max en route +8 min · last fix heading to — +8 min

Distribution · 90 days

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

  • Early 5% · 2
  • On time 88% · 35
  • 3–10 min 5% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 88% T n=8
  • 100% W n=8
  • 88% 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 (3 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
15:16on time +3 min
15:21≈ on time ≈ +2 min
15:24on time +2 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
Thu 5 NovKadaň 15:24No data—
Wed 4 NovKadaň 15:25No data—
Tue 3 NovKadaň 15:24No data—
Mon 2 NovKadaň 15:24No data—
Fri 30 OctKadaň 15:25No data—
Thu 29 OctKadaň 15:25No data—
Tue 27 OctKadaň 15:25No data—
Mon 26 OctKadaň 15:25No data—
Fri 23 OctKadaň 15:25No data—
Thu 22 OctKadaň 15:25No data—
Wed 21 OctKadaň 15:25No data—
Tue 20 OctKadaň 15:25No data—
Mon 19 OctKadaň 15:25No data—
Fri 16 OctKadaň 15:25No data—
Thu 15 OctKadaň 15:25No data—
Wed 14 OctKadaň 15:25No data—
Tue 13 OctKadaň 15:25No data—
Mon 12 OctKadaň 15:25No data—
Fri 9 OctKadaň 15:25No data—
Thu 8 OctKadaň 15:25No data—
Wed 7 OctKadaň 15:25No data—
Tue 6 OctKadaň 15:25No data—
Mon 5 Oct— 15:410 min—
Fri 2 Oct— 15:420 min—
Thu 1 Oct— 15:410 min—
Wed 30 Sept— 15:420 min—
Tue 29 Sept— 15:410 min—
Fri 25 Sept— 15:420 min—
Thu 24 Sept— 15:410 min—
Wed 23 Sept— 15:420 min—