Os 20302 20302 Kralupy n.V. – Velvary

View line Os 20302

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

It has not run yet today

Last recorded run: Wednesday 4 November −1 min

Next service: today 04:44 from Kralupy n.V. · Thu 5 Nov

Full trip card
Next departure 04:44 today · Kralupy n.V.
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
97%
86/89 runs under 3 min
RT coverage: 89 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Velvary, 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 +9 min · last fix heading to — +9 min
  • Sat 24 Oct Max en route +3 min · last fix heading to Velvary +3 min
  • Fri 16 Oct Max en route +3 min · last fix heading to Velvary +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 86
  • 3–10 min 3% · 3
  • 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=12
  • 92% F n=12
  • 92% 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, 89 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
Kralupy n.V.
04:44on time +1 min
Kralupy nad Vltavou předměstí
04:47 / 04:48≈ on time ≈ +1 min
Olovnice zastávka
04:53≈ on time ≈ +1 min
Velká Bučina
04:57≈ on time ≈ +1 min
Velvary
05:03on 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
Wed 4 NovVelvary 05:04−1 min+1 min
Tue 3 NovVelvary 05:05+1 min+2 min
Mon 2 NovVelvary 05:04+1 min+4 min
Sun 1 NovVelvary 05:09+2 min+2 min
Sat 31 OctVelvary 05:07+1 min+1 min
Fri 30 OctVelvary 05:09+1 min+1 min
Thu 29 OctVelvary 05:08+2 min+2 min
Wed 28 OctVelvary 05:06+2 min+2 min
Tue 27 OctVelvary 05:04+2 min+2 min
Mon 26 OctVelvary 05:08+1 min+1 min
Sun 25 OctVelvary 05:07+2 min+2 min
Sat 24 OctVelvary 05:04+3 min+3 min
Fri 23 OctVelvary 05:070 min+1 min
Thu 22 OctVelvary 05:08+1 min+2 min
Wed 21 OctVelvary 05:09+1 min+2 min
Tue 20 OctVelvary 05:080 min+1 min
Mon 19 OctVelvary 05:06+1 min+1 min
Sun 18 OctVelvary 05:08+2 min+2 min
Sat 17 OctVelvary 05:08+1 min+2 min
Fri 16 OctVelvary 05:08+3 min+3 min
Thu 15 OctVelvary 05:080 min+1 min
Wed 14 OctVelvary 05:05+2 min+2 min
Tue 13 OctVelvary 05:09+2 min+2 min
Mon 12 OctVelvary 05:06−1 min+1 min
Sun 11 OctVelvary 05:04+1 min+1 min
Sat 10 OctVelvary 05:080 min+2 min
Fri 9 OctVelvary 05:040 min+1 min
Thu 8 OctVelvary 05:070 min+1 min
Wed 7 OctVelvary 05:07+1 min+1 min
Tue 6 OctVelvary 05:08+1 min+1 min