Os 17167 17167 Kladno-Ostrovec – Kladno

View line Os 17167

Kladno-Ostrovec 14:03 → Kladno 14:10 Daily 0 h 07 min · 3 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Kladno at 14:10 0 min

  1. Kladno-Ostrovec14:03
  2. Kladno město14:05
  3. Kladno14:10

Next service: tomorrow 14:03 from Kladno-Ostrovec · Wed 11 Nov

Next departure 14:03 tomorrow · Kladno-Ostrovec
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
82/82 runs under 3 min
RT coverage: 82 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Kladno, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 82
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=12
  • 100% W n=10
  • 100% T n=12
  • 100% F n=12
  • 100% S n=12
  • 100% S n=12

Stops and timetable

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

Last 90 days, 82 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
14:03on time +1 min
14:05 / 14:06≈ on time ≈ +1 min
14:101 min early 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
Tue 10 NovKladno 14:140 min—
Mon 9 NovKladno 14:14+1 min+1 min
Sun 8 NovKladno 14:13−1 min—
Sat 7 NovKladno 14:13−1 min—
Fri 6 NovKladno 14:14−1 min—
Thu 5 NovKladno 14:14−1 min—
Wed 4 NovKladno 14:13−1 min+1 min
Tue 3 NovKladno 14:14−1 min—
Mon 2 NovKladno 14:13−1 min—
Sun 1 NovKladno 14:140 min+1 min
Sat 31 OctKladno 14:140 min—
Fri 30 OctKladno 14:13−1 min—
Thu 29 OctKladno 14:13−1 min—
Wed 28 OctKladno 14:140 min—
Tue 27 OctKladno 14:140 min+1 min
Mon 26 OctKladno 14:14−1 min—
Sun 25 OctKladno 14:140 min—
Sat 24 OctKladno 14:140 min—
Fri 23 OctKladno 14:140 min+1 min
Thu 22 OctKladno 14:140 min—
Wed 21 OctKladno 14:13−1 min—
Tue 20 OctKladno 14:13−1 min—
Mon 19 OctKladno 14:14+1 min+1 min
Sun 18 OctKladno 14:14−1 min—
Sat 17 OctKladno 14:140 min+1 min
Fri 16 OctKladno 14:14−1 min—
Thu 15 OctKladno 14:14−1 min—
Wed 14 OctKladno 14:11No data—
Tue 13 OctKladno 14:140 min—
Mon 12 OctKladno 14:150 min+1 min