Os 25952 25952 Praha-Vršovice – Hostivice

View line Os 25952

Praha-Vršovice 06:10 → Hostivice 06:50 Sat, Sun 0 h 40 min · 9 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 1 November −1 min

Next service: tomorrow 06:10 from Praha-Vršovice · Sat 7 Nov

Next departure 06:10 tomorrow · Praha-Vršovice
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 9 full · 0 partial · 0 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 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 Hostivice, 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

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

  • Early 4% · 1
  • On time 96% · 24
  • 3–10 min 0% · 0
  • 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=11
  • 100% S n=12

Stops and timetable

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

Last 90 days, 25 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
06:10on time +1 min
06:17≈ on time ≈ +1 min
06:31 / 06:32≈ 1 min early ≈ on time
06:35≈ 1 min early ≈ on time
06:36≈ 1 min early ≈ on time
06:38≈ 1 min early ≈ on time
06:41 / 06:44≈ 1 min early ≈ on time
06:47≈ 1 min early ≈ on time
06:501 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 1 NovHostivice 06:53−1 min—
Sat 31 OctHostivice 06:53−1 min—
Wed 28 OctHostivice 06:54−1 min—
Sun 25 OctHostivice 06:54−1 min—
Sat 24 OctHostivice 06:54−1 min+1 min
Sun 18 OctHostivice 06:510 min—
Sat 17 OctHostivice 06:57+2 min+3 min
Sun 11 OctHostivice 06:54−1 min—
Sat 10 OctHostivice 06:550 min—
Sun 4 Oct— 07:050 min—
Sat 3 Oct— 07:03−1 min—
Mon 28 Sept— 07:050 min+1 min
Sun 27 Sept— 07:04−1 min—
Sat 26 Sept— 07:05+1 min+1 min
Sun 20 Sept— 07:03−1 min—
Sat 19 Sept— 07:04−1 min—
Sun 13 Sept— 07:03−1 min—
Sat 12 Sept— 07:04−1 min—
Sun 6 Sept— 07:040 min—
Sat 5 Sept— 07:03−1 min—
Sun 30 Aug— 07:03−1 min—
Sat 29 Aug— 07:02−2 min—
Sun 16 Aug— 07:03−1 min—
Sat 15 Aug— 07:03−1 min—
Sun 9 Aug— 07:03−1 min—