Os 18362 18362 Kadaň – Kadaňský Rohozec

View line Os 18362

Kadaň 10:10 → Kadaňský Rohozec 10:58 Sat, Sun 0 h 48 min · 11 stops Railway Capital a.s.

✓ Today’s run finished

Today, last fix heading to Kadaňský Rohozec at 10:59 No data

  1. Kadaň10:10
  2. Želina10:15
  3. Hradec u Kadaně10:20
  4. Pětipsy10:36
  5. Vilémov u Kadaně město10:44
  6. Radonice u Kadaně10:50
  7. Kadaňský Rohozec10:58
On-time · 30 days
—
Too little data (0/11 runs with data)
RT coverage: 0 full · 0 partial · 11 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 17 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
P90
0min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Kadaňský Rohozec, 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 28 Sept Max en route +8 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 17 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
10:10on time +2 min
10:11≈ on time ≈ +2 min
10:15 / 10:16≈ on time ≈ +2 min
10:20≈ on time ≈ +2 min
10:27 / 10:28≈ on time ≈ +2 min
10:36≈ on time ≈ +1 min
10:39 / 10:40≈ on time ≈ +1 min
10:44≈ on time ≈ +1 min
10:50≈ on time ≈ +1 min
10:55≈ on time ≈ +1 min
10:58on time on time

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 NovKadaňský Rohozec 10:59No data—
Sat 7 NovKadaňský Rohozec 10:59No data—
Sun 1 NovKadaňský Rohozec 10:59No data—
Sat 31 OctKadaňský Rohozec 10:59No data—
Wed 28 OctKadaňský Rohozec 10:59No data—
Sun 25 OctKadaňský Rohozec 10:59No data—
Sat 24 OctKadaňský Rohozec 10:59No data—
Sun 18 OctKadaňský Rohozec 10:59No data—
Sat 17 OctKadaňský Rohozec 10:59No data—
Sun 11 OctKadaňský Rohozec 10:59No data—
Sat 10 OctKadaňský Rohozec 10:59No data—
Sun 4 Oct— 11:390 min+1 min
Sat 3 Oct— 11:400 min+3 min
Mon 28 Sept— 11:46+7 min+8 min
Sun 27 Sept— 11:390 min+1 min
Sat 26 Sept— 11:400 min+1 min
Sun 20 Sept— 11:400 min+3 min
Sat 19 Sept— 11:41+1 min+3 min
Sun 13 Sept— 11:390 min—
Sat 12 Sept— 11:400 min—
Sun 6 Sept— 11:120 min—
Sat 5 Sept— 11:130 min+1 min
Sun 30 Aug— 11:120 min+1 min
Sat 29 Aug— 11:130 min+2 min
Sun 23 Aug— 11:120 min+1 min
Sat 22 Aug— 11:120 min+1 min
Sun 16 Aug— 11:120 min—
Sat 15 Aug— 11:120 min+2 min