Os 17171 17171 Kladno-Ostrovec – Kladno

View line Os 17171

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 18:03 from Kladno-Ostrovec · Tue 10 Nov

Next departure 18:03 today · Kladno-Ostrovec
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
100%
82/82 runs under 3 min
RT coverage: 82 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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=11
  • 100% W n=11
  • 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
18:03on time +1 min
18:05 / 18:06≈ on time ≈ +1 min
18:10on 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
Mon 9 NovKladno 18:140 min—
Sun 8 NovKladno 18:13−1 min—
Sat 7 NovKladno 18:14−1 min+1 min
Fri 6 NovKladno 18:140 min+1 min
Thu 5 NovKladno 18:09+1 min+1 min
Wed 4 NovKladno 18:150 min—
Tue 3 NovKladno 18:140 min+1 min
Mon 2 NovKladno 18:13−1 min—
Sun 1 NovKladno 18:140 min+1 min
Sat 31 OctKladno 18:140 min—
Fri 30 OctKladno 18:13−1 min—
Thu 29 OctKladno 18:150 min—
Wed 28 OctKladno 18:140 min—
Tue 27 OctKladno 18:140 min+1 min
Mon 26 OctKladno 18:140 min—
Sun 25 OctKladno 18:140 min—
Sat 24 OctKladno 18:140 min—
Fri 23 OctKladno 18:140 min—
Thu 22 OctKladno 18:14−1 min+1 min
Wed 21 OctKladno 18:140 min+1 min
Tue 20 OctKladno 18:140 min+1 min
Mon 19 OctKladno 18:13−1 min+1 min
Sun 18 OctKladno 18:110 min—
Sat 17 OctKladno 18:14−1 min+1 min
Fri 16 OctKladno 18:140 min—
Thu 15 OctKladno 18:14−1 min—
Wed 14 OctKladno 18:140 min—
Tue 13 OctKladno 18:140 min—
Mon 12 OctKladno 18:140 min+1 min
Sun 11 OctKladno 18:13−1 min—