Os 20352 20352 Kralupy n.V. – Velvary

View line Os 20352

Kralupy n.V. 06:49 → Velvary 07:08 Sat, Sun 0 h 19 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 8 November 0 min

Next service: Saturday 06:49 from Kralupy n.V. · Sat 14 Nov

Next departure 06:49 Saturday · Kralupy n.V.
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 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: +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

  • Sat 31 Oct Max en route +3 min · last fix heading to Velvary +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 27
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • — T n=0
  • 100% W n=1
  • — T n=0
  • — F n=0
  • 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, 28 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
06:49on time +2 min
06:52 / 06:53≈ on time ≈ +2 min
06:58≈ on time ≈ +2 min
07:02≈ on time ≈ +2 min
07:08on 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
Sun 8 NovVelvary 07:130 min+3 min
Sat 7 NovVelvary 07:120 min+2 min
Sun 1 NovVelvary 07:090 min+2 min
Sat 31 OctVelvary 07:09+3 min+3 min
Wed 28 OctVelvary 07:11+1 min+4 min
Sun 25 OctVelvary 07:10+1 min+4 min
Sat 24 OctVelvary 07:120 min+2 min
Sun 18 OctVelvary 07:100 min+1 min
Sat 17 OctVelvary 07:14+2 min+3 min
Sun 11 OctVelvary 07:130 min+2 min
Sat 10 OctVelvary 07:13+1 min+1 min
Sun 4 Oct— 07:230 min—
Sat 3 Oct— 07:220 min—
Mon 28 Sept— 07:24+1 min+1 min
Sun 27 Sept— 07:230 min+3 min
Sat 26 Sept— 07:230 min—
Sun 20 Sept— 07:220 min—
Sat 19 Sept— 07:240 min—
Sun 13 Sept— 07:220 min—
Sat 12 Sept— 07:24+1 min+3 min
Sun 6 Sept— 07:220 min—
Sat 5 Sept— 07:220 min—
Sun 30 Aug— 07:220 min—
Sat 29 Aug— 07:220 min+1 min
Sun 23 Aug— 07:220 min—
Sat 22 Aug— 07:220 min+2 min
Sun 16 Aug— 07:220 min—
Sat 15 Aug— 07:220 min—