Os 28252 28252 Úvaly – Praha hl. n.

View line Os 28252

Úvaly 18:12 → Praha hl. n. 18:40 Mon, Tue, Wed, Thu, Fri 0 h 28 min · 8 stops RegioJet a.s.

It has not run yet today

Last recorded run: Wednesday 4 November −5 min

Next service: today 18:12 from Úvaly · Thu 5 Nov

Next departure 18:12 today · Úvaly
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
92%
56/61 runs under 3 min
RT coverage: 61 full · 0 partial · 0 no data
Typical delay
−2min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Praha hl. n., in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 11 Sept Max en route +9 min · last fix heading to — +6 min
  • Wed 7 Oct Max en route +4 min · last fix heading to Praha hl. n. +4 min
  • Mon 10 Aug Max en route +4 min · last fix heading to — +4 min
  • Fri 16 Oct Max en route +6 min · last fix heading to Praha hl. n. +3 min
  • Thu 13 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 52% · 32
  • On time 39% · 24
  • 3–10 min 8% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 100% T n=13
  • 92% W n=12
  • 92% T n=12
  • 83% F n=12
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 61 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:12+1 min +4 min
18:15 / 18:16≈ on time ≈ +3 min
18:19≈ on time ≈ +3 min
18:21 / 18:22≈ on time ≈ +3 min
18:24 / 18:25≈ on time ≈ +2 min
18:27≈ on time ≈ +2 min
18:31 / 18:34≈ 1 min early ≈ +2 min
18:402 min early +2 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
Wed 4 NovPraha hl. n. 18:39−5 min+3 min
Tue 3 NovPraha hl. n. 18:47+2 min+8 min
Mon 2 NovPraha hl. n. 18:39−3 min+1 min
Fri 30 OctPraha hl. n. 18:46+1 min+1 min
Thu 29 OctPraha hl. n. 18:47+2 min+2 min
Tue 27 OctPraha hl. n. 18:42−5 min—
Mon 26 OctPraha hl. n. 18:41−4 min—
Fri 23 OctPraha hl. n. 18:420 min+2 min
Thu 22 OctPraha hl. n. 18:41−1 min+1 min
Wed 21 OctPraha hl. n. 18:440 min+3 min
Tue 20 OctPraha hl. n. 18:42−3 min+1 min
Mon 19 OctPraha hl. n. 18:45+1 min+1 min
Fri 16 OctPraha hl. n. 18:41+3 min+6 min
Thu 15 OctPraha hl. n. 18:450 min+1 min
Wed 14 OctPraha hl. n. 18:41−5 min+2 min
Tue 13 OctPraha hl. n. 18:45+1 min+3 min
Mon 12 OctPraha hl. n. 18:43−2 min+2 min
Fri 9 OctPraha hl. n. 18:41−3 min+2 min
Thu 8 OctPraha hl. n. 18:41−4 min+1 min
Wed 7 OctPraha hl. n. 18:42+4 min+4 min
Tue 6 OctPraha hl. n. 18:42−3 min+3 min
Mon 5 OctPraha hl. n. 18:410 min+2 min
Fri 2 Oct— 18:52−3 min—
Thu 1 Oct— 18:560 min+1 min
Wed 30 Sept— 18:56+1 min+4 min
Tue 29 Sept— 18:50−4 min—
Fri 25 Sept— 18:57+2 min+3 min
Thu 24 Sept— 18:52−3 min+1 min
Wed 23 Sept— 18:51−4 min—
Tue 22 Sept— 18:52−2 min+2 min