Os 25956 25956 Praha-Zličín – Hostivice

View line Os 25956

Praha-Zličín 21:41 → Hostivice 21:47 Tue, Sat, Sun 0 h 06 min · 3 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: Saturday 21:41 from Praha-Zličín · Sat 14 Nov

Next departure 21:41 Saturday · Praha-Zličín
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 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

  • Sun 16 Aug Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 8% · 2
  • On time 88% · 23
  • 3–10 min 4% · 1
  • 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
  • 100% S n=12
  • 92% S n=12

Stops and timetable

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

Last 90 days, 26 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
21:41on time +1 min
21:44≈ on time ≈ +1 min
21:471 min early +1 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 NovHostivice 21:490 min+1 min
Sat 7 NovHostivice 21:49−1 min—
Sun 1 NovHostivice 21:49−1 min—
Sat 31 OctHostivice 21:51+1 min+1 min
Wed 28 OctHostivice 21:520 min—
Sun 25 OctHostivice 21:510 min—
Sat 24 OctHostivice 21:52+1 min+1 min
Sun 18 OctHostivice 21:480 min+1 min
Sat 17 OctHostivice 21:480 min—
Sun 11 OctHostivice 21:51−1 min—
Sat 10 OctHostivice 21:510 min—
Sun 4 Oct— 22:02+1 min+3 min
Sat 3 Oct— 22:01−1 min—
Mon 28 Sept— 22:01−1 min—
Sun 27 Sept— 22:00−1 min—
Sat 26 Sept— 22:00−1 min—
Sun 20 Sept— 21:59−2 min—
Sat 19 Sept— 22:00−1 min—
Sun 13 Sept— 22:00−1 min—
Sat 12 Sept— 22:010 min—
Sun 6 Sept— 22:00−1 min—
Sat 5 Sept— 22:00−1 min—
Sun 30 Aug— 22:00−1 min—
Sat 29 Aug— 22:00−1 min—
Sun 16 Aug— 22:07+5 min+6 min
Sat 15 Aug— 21:59−2 min—