Os 20303 20303 Velvary – Kralupy n.V.

View line Os 20303

Velvary 05:10 → Kralupy n.V. 05:29 Daily 0 h 19 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Kralupy n.V. at 05:29 0 min

  1. Velvary05:10
  2. Velká Bučina05:14
  3. Olovnice zastávka05:19
  4. Kralupy nad Vltavou předměstí05:25
  5. Kralupy n.V.05:29

Next service: tomorrow 05:10 from Velvary · Fri 6 Nov

Full trip card
Next departure 05:10 tomorrow · Velvary
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
99%
89/90 runs under 3 min
RT coverage: 90 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Kralupy n.V., 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 1 Oct Max en route +7 min · last fix heading to — +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 99% · 89
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 90 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
Velvary
05:10on time on time
Velká Bučina
05:14≈ on time ≈ on time
Olovnice zastávka
05:19≈ on time ≈ on time
Kralupy nad Vltavou předměstí
05:25≈ on time ≈ +1 min
Kralupy n.V.
05:29on time +1 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
Thu 5 NovKralupy n.V. 05:330 min+1 min
Wed 4 NovKralupy n.V. 05:330 min+1 min
Tue 3 NovKralupy n.V. 05:34+1 min+1 min
Mon 2 NovKralupy n.V. 05:290 min+1 min
Sun 1 NovKralupy n.V. 05:300 min+2 min
Sat 31 OctKralupy n.V. 05:34+1 min+1 min
Fri 30 OctKralupy n.V. 05:310 min+2 min
Thu 29 OctKralupy n.V. 05:330 min+2 min
Wed 28 OctKralupy n.V. 05:340 min—
Tue 27 OctKralupy n.V. 05:30−1 min+2 min
Mon 26 OctKralupy n.V. 05:330 min+1 min
Sun 25 OctKralupy n.V. 05:35+1 min+2 min
Sat 24 OctKralupy n.V. 05:330 min+1 min
Fri 23 OctKralupy n.V. 05:33−1 min—
Thu 22 OctKralupy n.V. 05:300 min+2 min
Wed 21 OctKralupy n.V. 05:340 min—
Tue 20 OctKralupy n.V. 05:330 min+2 min
Mon 19 OctKralupy n.V. 05:32−1 min+2 min
Sun 18 OctKralupy n.V. 05:32−1 min—
Sat 17 OctKralupy n.V. 05:34+1 min+1 min
Fri 16 OctKralupy n.V. 05:300 min+1 min
Thu 15 OctKralupy n.V. 05:330 min—
Wed 14 OctKralupy n.V. 05:34+1 min+2 min
Tue 13 OctKralupy n.V. 05:34+1 min+1 min
Mon 12 OctKralupy n.V. 05:330 min+2 min
Sun 11 OctKralupy n.V. 05:34+1 min+1 min
Sat 10 OctKralupy n.V. 05:330 min+1 min
Fri 9 OctKralupy n.V. 05:32−1 min—
Thu 8 OctKralupy n.V. 05:30−1 min—
Wed 7 OctKralupy n.V. 05:34+1 min+1 min