Os 20322 20322 Kralupy n.V. – Velvary

View line Os 20322

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

✓ Today’s run finished

Today it reached Velvary at 14:47 +2 min

  1. Kralupy n.V.14:26
  2. Kralupy nad Vltavou předměstí14:29
  3. Olovnice zastávka14:35
  4. Velká Bučina14:39
  5. Velvary14:45

Next service: tomorrow 14:26 from Kralupy n.V. · Fri 6 Nov

Next departure 14:26 tomorrow · Kralupy n.V.
On-time · 30 days
53%
16/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
81%
73/90 runs under 3 min
RT coverage: 90 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +3 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +8 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

  • Wed 21 Oct Max en route +13 min · last fix heading to Velvary +13 min
  • Fri 16 Oct Max en route +11 min · last fix heading to Velvary +9 min
  • Tue 29 Sept Max en route +11 min · last fix heading to — +9 min
  • Wed 28 Oct Max en route +8 min · last fix heading to Velvary +8 min
  • Thu 15 Oct Max en route +9 min · last fix heading to Velvary +8 min

Distribution · 90 days

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

  • Early 2% · 2
  • On time 79% · 71
  • 3–10 min 18% · 16
  • 10–30 min 1% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=13
  • 85% T n=13
  • 77% W n=13
  • 77% T n=13
  • 75% F n=12
  • 92% S n=13
  • 69% 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
14:26on time +4 min
14:29 / 14:30≈ on time ≈ +4 min
14:35≈ on time ≈ +4 min
14:39≈ on time ≈ +4 min
14:45on time +4 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 NovVelvary 14:49+2 min+4 min
Wed 4 NovVelvary 14:54+4 min+5 min
Tue 3 NovVelvary 14:49+1 min+1 min
Mon 2 NovVelvary 14:49+1 min+1 min
Sun 1 NovVelvary 14:57+7 min+9 min
Sat 31 OctVelvary 14:47+2 min+6 min
Fri 30 OctVelvary 14:51+3 min+3 min
Thu 29 OctVelvary 14:50+2 min+2 min
Wed 28 OctVelvary 14:55+8 min+8 min
Tue 27 OctVelvary 14:46−1 min+1 min
Mon 26 OctVelvary 14:52+3 min+3 min
Sun 25 OctVelvary 14:52+3 min+5 min
Sat 24 OctVelvary 14:500 min+2 min
Fri 23 OctVelvary 14:50+3 min+3 min
Thu 22 OctVelvary 14:48+4 min+4 min
Wed 21 OctVelvary 15:00+13 min+13 min
Tue 20 OctVelvary 14:48−2 min+1 min
Mon 19 OctVelvary 14:46+2 min+2 min
Sun 18 OctVelvary 14:53+3 min+7 min
Sat 17 OctVelvary 14:46+2 min+2 min
Fri 16 OctVelvary 14:59+9 min+11 min
Thu 15 OctVelvary 14:58+8 min+9 min
Wed 14 OctVelvary 14:52+2 min+2 min
Tue 13 OctVelvary 14:46+2 min+3 min
Mon 12 OctVelvary 14:490 min+2 min
Sun 11 OctVelvary 14:53+3 min+4 min
Sat 10 OctVelvary 14:48+3 min+4 min
Fri 9 OctVelvary 14:500 min+1 min
Thu 8 OctVelvary 14:52+3 min+3 min
Wed 7 OctVelvary 14:50+1 min+2 min