Os 19759 19759 Středokluky – Hostivice

View line Os 19759

Středokluky 16:58 → Hostivice 17:13 Daily 0 h 15 min · 6 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 16:58 from Středokluky · Mon 16 Nov

Next departure 16:58 today · Středokluky
On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 24 full · 0 partial · 5 no data
On-time · 90 days
96%
75/78 runs under 3 min
RT coverage: 78 full · 0 partial · 5 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: +1 min

Last 30 days

Arrival delay at Hostivice, 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 8 Nov Max en route +4 min · last fix heading to Hostivice +4 min
  • Sat 26 Sept Max en route +4 min · last fix heading to — +4 min
  • Wed 9 Sept Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 24% · 19
  • On time 72% · 56
  • 3–10 min 4% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 78 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
16:58on time +1 min
17:02≈ on time ≈ on time
17:03≈ on time ≈ on time
17:04≈ on time ≈ on time
17:07≈ 1 min early ≈ on time
17:131 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
Sun 15 NovHostivice 17:170 min+2 min
Sat 14 NovHostivice 17:14−2 min—
Fri 13 NovHostivice 17:14−1 min+1 min
Thu 12 NovHostivice 17:14−1 min—
Wed 11 NovHostivice 17:14−1 min—
Tue 10 NovHostivice 17:14−2 min+1 min
Mon 9 NovHostivice 17:14−1 min+1 min
Sun 8 NovHostivice 17:19+4 min+4 min
Sat 7 NovHostivice 17:19+1 min+2 min
Fri 6 NovHostivice 17:17−1 min—
Thu 5 NovHostivice 17:170 min+1 min
Wed 4 NovHostivice 17:14−1 min—
Tue 3 NovHostivice 17:180 min+1 min
Mon 2 NovHostivice 17:14−1 min+1 min
Sun 1 NovHostivice 17:17−1 min—
Sat 31 OctHostivice 17:14+1 min+1 min
Fri 30 OctHostivice 17:14No data—
Thu 29 OctHostivice 17:14No data—
Wed 28 OctHostivice 17:14No data—
Tue 27 OctHostivice 17:15No data—
Mon 26 OctHostivice 17:14No data—
Sun 25 OctHostivice 17:17−1 min—
Sat 24 OctHostivice 17:16−2 min—
Fri 23 OctHostivice 17:160 min—
Thu 22 OctHostivice 17:14−1 min—
Wed 21 OctHostivice 17:17−1 min—
Tue 20 OctHostivice 17:17−1 min—
Mon 19 OctHostivice 17:16−1 min+1 min
Sun 18 OctHostivice 17:140 min—
Sat 17 OctHostivice 17:16−1 min—