Os 20301 20301 Velvary – Kralupy n.V.

View line Os 20301

Velvary 04:18 → Kralupy n.V. 04:37 Mon, Tue, Wed, Thu, Fri 0 h 19 min · 5 stops České dráhy, a.s.

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 04:18 from Velvary · Mon 9 Nov

Next departure 04:18 today · Velvary
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
100%
61/61 runs under 3 min
RT coverage: 61 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: +1 min

Last 30 days

Arrival delay at Kralupy n.V., 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

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

  • Early 0% · 0
  • On time 100% · 61
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=12
  • 100% W n=12
  • 100% 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, 61 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
04:18on time on time
04:22≈ on time ≈ on time
04:27≈ on time ≈ on time
04:33≈ on time ≈ +1 min
04:37on 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
Fri 6 NovKralupy n.V. 04:390 min+1 min
Thu 5 NovKralupy n.V. 04:380 min+1 min
Wed 4 NovKralupy n.V. 04:39+1 min+1 min
Tue 3 NovKralupy n.V. 04:390 min+1 min
Mon 2 NovKralupy n.V. 04:42+1 min+2 min
Fri 30 OctKralupy n.V. 04:420 min+2 min
Thu 29 OctKralupy n.V. 04:420 min+2 min
Tue 27 OctKralupy n.V. 04:410 min+1 min
Mon 26 OctKralupy n.V. 04:410 min+1 min
Fri 23 OctKralupy n.V. 04:410 min—
Thu 22 OctKralupy n.V. 04:410 min—
Wed 21 OctKralupy n.V. 04:43+1 min+2 min
Tue 20 OctKralupy n.V. 04:380 min+2 min
Mon 19 OctKralupy n.V. 04:410 min+1 min
Fri 16 OctKralupy n.V. 04:410 min+2 min
Thu 15 OctKralupy n.V. 04:42+1 min+1 min
Wed 14 OctKralupy n.V. 04:410 min+2 min
Tue 13 OctKralupy n.V. 04:420 min+2 min
Mon 12 OctKralupy n.V. 04:38−1 min+1 min
Fri 9 OctKralupy n.V. 04:410 min+1 min
Thu 8 OctKralupy n.V. 04:40−1 min+1 min
Wed 7 OctKralupy n.V. 04:44+2 min+2 min
Tue 6 OctKralupy n.V. 04:410 min+1 min
Mon 5 Oct— 04:510 min—
Fri 2 Oct— 04:510 min—
Thu 1 Oct— 05:330 min—
Wed 30 Sept— 04:510 min—
Tue 29 Sept— 04:510 min—
Fri 25 Sept— 04:520 min—
Thu 24 Sept— 04:510 min—