Os 19765 19765 Středokluky – Hostivice

View line Os 19765

Středokluky 20:03 → Hostivice 20:18 Mon, Tue, Wed, Thu, Fri 0 h 15 min · 6 stops České dráhy, a.s.

It does not run today

Last recorded run: Friday 13 November −2 min

Next service: tomorrow 20:03 from Středokluky · Mon 16 Nov

Full trip card
Next departure 20:03 tomorrow · Středokluky
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 15 full · 0 partial · 4 no data
On-time · 90 days
98%
52/53 runs under 3 min
RT coverage: 53 full · 0 partial · 4 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: −2 min
P90
−1min
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

  • Thu 8 Oct Max en route +5 min · last fix heading to Hostivice +3 min

Distribution · 90 days

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

  • Early 77% · 41
  • On time 21% · 11
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 100% T n=11
  • 100% W n=11
  • 91% T n=11
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 53 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
Středokluky
20:03on time on time
Dobrovíz
20:07≈ 1 min early ≈ on time
Dobrovíz-Amazon
20:08≈ 1 min early ≈ on time
Hostouň u Prahy
20:09≈ 1 min early ≈ on time
Jeneč zastávka
20:12≈ 1 min early ≈ on time
Hostivice
20:182 min early 1 min early

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
Fri 13 NovHostivice 20:19−2 min—
Thu 12 NovHostivice 20:19−2 min—
Wed 11 NovHostivice 20:190 min—
Tue 10 NovHostivice 20:19−2 min—
Mon 9 NovHostivice 20:22−1 min+1 min
Fri 6 NovHostivice 20:19−3 min—
Thu 5 NovHostivice 20:19−2 min—
Wed 4 NovHostivice 20:19−2 min+1 min
Tue 3 NovHostivice 20:19−2 min—
Mon 2 NovHostivice 20:19−2 min+1 min
Fri 30 OctHostivice 20:19No data—
Thu 29 OctHostivice 20:19No data—
Tue 27 OctHostivice 20:20No data—
Mon 26 OctHostivice 20:19No data—
Fri 23 OctHostivice 20:21−2 min—
Thu 22 OctHostivice 20:21−2 min+2 min
Wed 21 OctHostivice 20:19−3 min—
Tue 20 OctHostivice 20:21−2 min—
Mon 19 OctHostivice 20:21−1 min+1 min
Fri 16 OctHostivice 20:20−2 min—
Thu 15 OctHostivice 20:21−1 min—
Wed 14 OctHostivice 20:21−1 min+1 min
Tue 13 OctHostivice 20:20−2 min—
Mon 12 OctHostivice 20:20−3 min—
Fri 9 OctHostivice 20:22−1 min+1 min
Thu 8 OctHostivice 20:26+3 min+5 min
Wed 7 OctHostivice 20:22−1 min+1 min
Tue 6 OctHostivice 20:22−1 min—
Mon 5 OctHostivice 20:20−2 min—
Fri 2 Oct— 20:31−1 min—