Os 17102 17102 Kladno – Kralupy n.V.

View line Os 17102

Kladno 04:58 → Kralupy n.V. 05:36 Sat, Sun 0 h 38 min · 12 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Kralupy n.V. at 05:38 +2 min

  1. Kladno04:58
  2. Kladno-Ostrovec05:04
  3. Kladno-Dubí05:10
  4. Brandýsek05:16
  5. Dřetovice05:20
  6. Otvovice05:28
  7. Kralupy n.V.05:36

Next service: Saturday 04:58 from Kladno · Sat 14 Nov

Next departure 04:58 Saturday · Kladno
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 11 full · 0 partial · 0 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Kralupy n.V., in minutes. One bar per run.

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

Worst days

  • Sun 1 Nov Max en route +7 min · last fix heading to Kralupy n.V. +3 min
  • Sat 10 Oct Max en route +3 min · last fix heading to Kralupy n.V. +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
04:58on time on time
05:01 / 05:02≈ on time ≈ on time
05:04≈ on time ≈ +1 min
05:08≈ on time ≈ +1 min
05:10≈ on time ≈ +1 min
05:13≈ on time ≈ +1 min
05:16 / 05:17≈ on time ≈ +1 min
05:20≈ +1 min ≈ +2 min
05:26≈ +1 min ≈ +2 min
05:28 / 05:29≈ +1 min ≈ +2 min
05:33≈ +1 min ≈ +2 min
05:36+1 min +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
Sun 8 NovKralupy n.V. 05:42+2 min+2 min
Sat 7 NovKralupy n.V. 05:43+2 min+2 min
Sun 1 NovKralupy n.V. 05:44+3 min+7 min
Sat 31 OctKralupy n.V. 05:43+2 min+2 min
Wed 28 OctKralupy n.V. 05:41+1 min+1 min
Sun 25 OctKralupy n.V. 05:42+2 min+5 min
Sat 24 OctKralupy n.V. 05:400 min+1 min
Sun 18 OctKralupy n.V. 05:41+1 min+2 min
Sat 17 OctKralupy n.V. 05:42+2 min+2 min
Sun 11 OctKralupy n.V. 05:37+1 min+1 min
Sat 10 OctKralupy n.V. 05:43+3 min+3 min
Sun 4 Oct— 05:510 min—
Sat 3 Oct— 05:52+2 min+2 min
Mon 28 Sept— 05:52+1 min+1 min
Sun 27 Sept— 05:510 min+5 min
Sat 26 Sept— 05:52+2 min+2 min
Sun 20 Sept— 05:500 min—
Sat 19 Sept— 05:50−1 min—
Sun 13 Sept— 05:51+1 min+1 min
Sat 12 Sept— 05:52+1 min+1 min
Sun 6 Sept— 05:51+1 min+1 min
Sat 5 Sept— 05:52+1 min+1 min
Sun 30 Aug— 05:51+1 min+1 min
Sat 29 Aug— 05:510 min—
Sun 23 Aug— 05:52+2 min+2 min
Sat 22 Aug— 06:290 min—
Sun 16 Aug— 05:500 min—
Sat 15 Aug— 05:51+1 min+2 min