Os 20350 20350 Kralupy n.V. – Velvary

View line Os 20350

Kralupy n.V. 05:49 → Velvary 06:13 Tue, Sat, Sun 0 h 24 min · 5 stops České dráhy, a.s.

It does not run today

Last recorded run: Sunday 15 November 0 min

Next service: tomorrow 05:49 from Kralupy n.V. · Tue 17 Nov

Next departure 05:49 tomorrow · Kralupy n.V.
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 10 full · 0 partial · 0 no data
On-time · 90 days
100%
28/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
0min
9 in 10 runs arrive with less than this
30 days: +1 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

Distribution · 90 days

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

  • Early 7% · 2
  • On time 93% · 26
  • 3–10 min 0% · 0
  • 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
  • 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, 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
05:49on time +1 min
05:52 / 05:58≈ on time ≈ +1 min
06:03≈ on time ≈ on time
06:08≈ on time ≈ on time
06:13on time on time

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 15 NovVelvary 06:140 min+1 min
Sat 14 NovVelvary 06:14−2 min—
Sun 8 NovVelvary 06:18+1 min+2 min
Sat 7 NovVelvary 06:140 min+1 min
Sun 1 NovVelvary 06:180 min+1 min
Sat 31 OctVelvary 06:180 min+1 min
Wed 28 OctVelvary 06:15+2 min+2 min
Sun 25 OctVelvary 06:180 min+1 min
Sat 24 OctVelvary 06:17−1 min+1 min
Sun 18 OctVelvary 06:15−1 min—
Sat 17 OctVelvary 06:18+1 min+1 min
Sun 11 OctVelvary 06:150 min+1 min
Sat 10 OctVelvary 06:15−2 min+1 min
Sun 4 Oct— 06:280 min—
Sat 3 Oct— 06:260 min—
Mon 28 Sept— 06:280 min—
Sun 27 Sept— 06:280 min—
Sat 26 Sept— 06:270 min—
Sun 20 Sept— 06:270 min+1 min
Sat 19 Sept— 06:280 min—
Sun 13 Sept— 06:270 min—
Sat 12 Sept— 06:280 min—
Sun 6 Sept— 06:27−1 min—
Sat 5 Sept— 06:280 min—
Sun 30 Aug— 06:270 min—
Sat 29 Aug— 06:270 min—
Sun 23 Aug— 06:270 min—
Sat 22 Aug— 06:270 min—