Os 28265 28265 Praha hl. n. – Úvaly

View line Os 28265

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

✓ Today’s run finished

Today it reached Úvaly at 21:48 0 min

  1. Praha hl. n.21:20
  2. Praha-Libeň21:26
  3. Praha-Kyje21:32
  4. Praha-Běchovice21:38
  5. Praha-Běchovice střed21:40
  6. Praha-Klánovice21:43
  7. Úvaly21:48

Next service: Monday 21:20 from Praha hl. n. · Mon 9 Nov

Next departure 21:20 Monday · Praha hl. n.
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 62 full · 0 partial · 1 no data
Typical delay
0min
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 Úvaly, 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 21 Aug Max en route +5 min · last fix heading to — +5 min
  • Tue 27 Oct Max en route +3 min · last fix heading to Úvaly +3 min
  • Wed 21 Oct Max en route +3 min · last fix heading to Úvaly +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 59
  • 3–10 min 5% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 92% T n=13
  • 92% W n=12
  • 100% T n=13
  • 92% 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, 62 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:20on time +2 min
21:26 / 21:29≈ on time ≈ +2 min
21:32 / 21:33≈ on time ≈ +1 min
21:35≈ on time ≈ +1 min
21:38≈ on time ≈ +1 min
21:40≈ on time ≈ +1 min
21:43 / 21:44≈ on time ≈ +2 min
21:48on time +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
Fri 6 NovÚvaly 21:490 min—
Thu 5 NovÚvaly 21:530 min—
Wed 4 NovÚvaly 21:520 min—
Tue 3 NovÚvaly 21:530 min+1 min
Mon 2 NovÚvaly 21:52+1 min+1 min
Fri 30 OctÚvaly 21:49+1 min+3 min
Thu 29 OctÚvaly 21:490 min—
Tue 27 OctÚvaly 21:55+3 min+3 min
Mon 26 OctÚvaly 21:52−1 min+1 min
Fri 23 OctÚvaly 21:49No data—
Thu 22 OctÚvaly 21:52−1 min+1 min
Wed 21 OctÚvaly 21:55+3 min+3 min
Tue 20 OctÚvaly 21:54+2 min+2 min
Mon 19 OctÚvaly 21:530 min—
Fri 16 OctÚvaly 21:52+1 min+1 min
Thu 15 OctÚvaly 21:520 min—
Wed 14 OctÚvaly 21:520 min+1 min
Tue 13 OctÚvaly 21:530 min+2 min
Mon 12 OctÚvaly 21:52+1 min+1 min
Fri 9 OctÚvaly 21:53+1 min+2 min
Thu 8 OctÚvaly 21:52+1 min+1 min
Wed 7 OctÚvaly 21:530 min—
Tue 6 OctÚvaly 21:520 min+1 min
Mon 5 OctÚvaly 21:520 min—
Fri 2 Oct— 22:020 min—
Thu 1 Oct— 22:020 min—
Wed 30 Sept— 22:020 min—
Tue 29 Sept— 22:020 min—
Fri 25 Sept— 22:03+1 min+1 min
Thu 24 Sept— 22:040 min+4 min