Os 28264 28264 Úvaly – Praha hl. n.

View line Os 28264

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

It has not run yet today

Last recorded run: Wednesday 4 November +2 min

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

Next departure 21:12 today · Úvaly
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 19 full · 0 partial · 1 no data
On-time · 90 days
88%
53/60 runs under 3 min
RT coverage: 60 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+3min
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

  • Thu 24 Sept Max en route +8 min · last fix heading to — +8 min
  • Fri 11 Sept Max en route +7 min · last fix heading to — +6 min
  • Wed 2 Sept Max en route +7 min · last fix heading to — +5 min
  • Mon 17 Aug Max en route +5 min · last fix heading to — +5 min
  • Tue 27 Oct Max en route +4 min · last fix heading to Praha hl. n. +3 min

Distribution · 90 days

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

  • Early 30% · 18
  • On time 58% · 35
  • 3–10 min 12% · 7
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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