Os 20312 20312 Kralupy n.V. – Velvary

View line Os 20312

Kralupy n.V. 09:26 → Velvary 09:46 Mon, Tue, Wed, Thu, Fri 0 h 20 min · 5 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Velvary at 09:48 +2 min

  1. Kralupy n.V.09:26
  2. Kralupy nad Vltavou předměstí09:29
  3. Olovnice zastávka09:35
  4. Velká Bučina09:40
  5. Velvary09:46

Next service: Wednesday 09:26 from Kralupy n.V. · Wed 18 Nov

Next departure 09:26 Wednesday · Kralupy n.V.
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 20 full · 0 partial · 0 no data
On-time · 90 days
85%
53/62 runs under 3 min
RT coverage: 62 full · 0 partial · 0 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: +4 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 20 Aug Max en route +9 min · last fix heading to — +7 min
  • Tue 20 Oct Max en route +7 min · last fix heading to Velvary +5 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Velvary +5 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Velvary +4 min
  • Tue 29 Sept Max en route +6 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 84% · 52
  • 3–10 min 15% · 9
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=12
  • 67% T n=12
  • 92% W n=12
  • 85% T n=13
  • 100% F n=13
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
09:26on time +2 min
09:29 / 09:30≈ on time ≈ +2 min
09:35≈ on time ≈ +2 min
09:40≈ on time ≈ +3 min
09:46on 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
Mon 16 NovVelvary 09:49+2 min+2 min
Fri 13 NovVelvary 09:49+1 min+2 min
Thu 12 NovVelvary 09:470 min+1 min
Wed 11 NovVelvary 09:48+1 min+1 min
Tue 10 NovVelvary 09:490 min+2 min
Mon 9 NovVelvary 09:53+4 min+4 min
Fri 6 NovVelvary 09:49+1 min+2 min
Thu 5 NovVelvary 09:49+1 min+4 min
Wed 4 NovVelvary 09:490 min+2 min
Tue 3 NovVelvary 09:49−1 min+3 min
Mon 2 NovVelvary 09:49+1 min+4 min
Fri 30 OctVelvary 09:500 min+2 min
Thu 29 OctVelvary 09:500 min+2 min
Tue 27 OctVelvary 09:49+3 min+3 min
Mon 26 OctVelvary 09:510 min+3 min
Fri 23 OctVelvary 09:510 min+2 min
Thu 22 OctVelvary 09:500 min+1 min
Wed 21 OctVelvary 09:52+2 min+2 min
Tue 20 OctVelvary 09:56+5 min+7 min
Mon 19 OctVelvary 09:54+5 min+5 min
Fri 16 OctVelvary 09:50+2 min+4 min
Thu 15 OctVelvary 09:47+2 min+2 min
Wed 14 OctVelvary 09:50+1 min+2 min
Tue 13 OctVelvary 09:48+1 min+3 min
Mon 12 OctVelvary 09:47+1 min+2 min
Fri 9 OctVelvary 09:51+1 min+1 min
Thu 8 OctVelvary 09:47−1 min+2 min
Wed 7 OctVelvary 09:49−1 min+1 min
Tue 6 OctVelvary 09:52+2 min+5 min
Mon 5 Oct— 10:000 min—