Os 20304 20304 Kralupy n.V. – Velvary

View line Os 20304

Kralupy n.V. 05:45 → Velvary 06:11 Mon, Tue, Wed, Thu, Fri 0 h 26 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 05:45 from Kralupy n.V. · Mon 9 Nov

Next departure 05:45 today · Kralupy n.V.
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
98%
60/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
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

Worst days

  • Fri 21 Aug Max en route +25 min · last fix heading to — +19 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 97% · 59
  • 3–10 min 0% · 0
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=12
  • 100% W n=12
  • 100% T n=13
  • 92% 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
05:45on time +1 min
05:48 / 05:56≈ on time ≈ +1 min
06:01≈ on time ≈ +1 min
06:06≈ on time ≈ +1 min
06:11on 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
Fri 6 NovVelvary 06:140 min+1 min
Thu 5 NovVelvary 06:140 min+1 min
Wed 4 NovVelvary 06:140 min+1 min
Tue 3 NovVelvary 06:130 min+1 min
Mon 2 NovVelvary 06:140 min+1 min
Fri 30 OctVelvary 06:16+1 min+2 min
Thu 29 OctVelvary 06:160 min+1 min
Tue 27 OctVelvary 06:13−1 min+1 min
Mon 26 OctVelvary 06:130 min+1 min
Fri 23 OctVelvary 06:14+1 min+4 min
Thu 22 OctVelvary 06:150 min+1 min
Wed 21 OctVelvary 06:130 min+1 min
Tue 20 OctVelvary 06:13+1 min+2 min
Mon 19 OctVelvary 06:150 min+1 min
Fri 16 OctVelvary 06:150 min+3 min
Thu 15 OctVelvary 06:140 min—
Wed 14 OctVelvary 06:13−2 min—
Tue 13 OctVelvary 06:16+2 min+2 min
Mon 12 OctVelvary 06:150 min+1 min
Fri 9 OctVelvary 06:130 min+1 min
Thu 8 OctVelvary 06:150 min+2 min
Wed 7 OctVelvary 06:150 min—
Tue 6 OctVelvary 06:13+1 min+1 min
Mon 5 Oct— 06:250 min+3 min
Fri 2 Oct— 06:260 min—
Thu 1 Oct— 06:260 min+3 min
Wed 30 Sept— 06:250 min—
Tue 29 Sept— 06:250 min—
Fri 25 Sept— 06:260 min—
Thu 24 Sept— 06:250 min—