Os 28224 28224 Úvaly – Praha hl. n.

View line Os 28224

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

It has not run yet today

Last recorded run: Friday 6 November −1 min

Next service: today 11:12 from Úvaly · Mon 9 Nov

Next departure 11:12 today · Úvaly
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
87%
52/60 runs under 3 min
RT coverage: 60 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Mon 17 Aug Max en route +8 min · last fix heading to — +8 min
  • Wed 12 Aug Max en route +8 min · last fix heading to — +8 min
  • Tue 3 Nov Max en route +7 min · last fix heading to Praha hl. n. +7 min
  • Tue 20 Oct Max en route +8 min · last fix heading to Praha hl. n. +7 min
  • Thu 20 Aug Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 35% · 21
  • On time 52% · 31
  • 3–10 min 13% · 8
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 91% M n=11
  • 83% T n=12
  • 92% W n=12
  • 85% T n=13
  • 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, 60 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
11:12on time +3 min
11:15 / 11:16≈ on time ≈ +3 min
11:19≈ on time ≈ +3 min
11:21 / 11:22≈ on time ≈ +3 min
11:24 / 11:25≈ on time ≈ +3 min
11:27≈ on time ≈ +3 min
11:31 / 11:32≈ on time ≈ +3 min
11:381 min early +3 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
Fri 6 NovPraha hl. n. 11:42−1 min—
Thu 5 NovPraha hl. n. 11:44+2 min+3 min
Wed 4 NovPraha hl. n. 11:390 min—
Tue 3 NovPraha hl. n. 11:49+7 min+7 min
Mon 2 NovPraha hl. n. 11:39−2 min—
Fri 30 OctPraha hl. n. 11:46+3 min+3 min
Thu 29 OctPraha hl. n. 11:39−1 min—
Tue 27 OctPraha hl. n. 11:40−2 min+2 min
Mon 26 OctPraha hl. n. 11:41−2 min+1 min
Fri 23 OctPraha hl. n. 11:41−2 min+1 min
Thu 22 OctPraha hl. n. 11:430 min+3 min
Wed 21 OctPraha hl. n. 11:40−3 min—
Tue 20 OctPraha hl. n. 11:44+7 min+8 min
Mon 19 OctPraha hl. n. 11:430 min+1 min
Fri 16 OctPraha hl. n. 11:45+2 min+2 min
Thu 15 OctPraha hl. n. 11:40−3 min—
Wed 14 OctPraha hl. n. 11:390 min—
Tue 13 OctPraha hl. n. 11:390 min+1 min
Mon 12 OctPraha hl. n. 11:420 min+2 min
Fri 9 OctPraha hl. n. 11:39+1 min+3 min
Thu 8 OctPraha hl. n. 11:41−2 min+1 min
Wed 7 OctPraha hl. n. 11:42−1 min+1 min
Tue 6 OctPraha hl. n. 11:41−2 min—
Mon 5 Oct— 11:51−1 min—
Fri 2 Oct— 11:50−2 min—
Thu 1 Oct— 11:51−2 min—
Wed 30 Sept— 11:520 min+1 min
Tue 29 Sept— 11:50−2 min+3 min
Fri 25 Sept— 11:50−2 min—
Thu 24 Sept— 11:52−1 min—