Os 9673 9673 Vraňany – Kralupy n.V.

View line Os 9673

Vraňany 08:19 → Kralupy n.V. 08:36 Mon, Tue, Wed, Thu, Fri 0 h 17 min · 6 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Kralupy n.V. at 08:36 0 min

  1. Vraňany08:19
  2. Mlčechvosty08:22
  3. Nové Ouholice08:25
  4. Nelahozeves08:28
  5. Nelahozeves zámek08:31
  6. Kralupy n.V.08:36

Next service: tomorrow 08:19 from Vraňany · Fri 6 Nov

Full trip card
Next departure 08:19 tomorrow · Vraňany
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 1 no data
On-time · 90 days
97%
59/61 runs under 3 min
RT coverage: 61 full · 0 partial · 1 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 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

Worst days

  • Thu 15 Oct Max en route +4 min · last fix heading to Kralupy n.V. +4 min
  • Thu 22 Oct Max en route +3 min · last fix heading to Kralupy n.V. +3 min

Distribution · 90 days

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

  • Early 10% · 6
  • On time 87% · 53
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 100% T n=13
  • 100% W n=12
  • 85% T n=13
  • 100% F n=11
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (6 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
Vraňany
08:19on time +1 min
Mlčechvosty
08:22≈ on time ≈ +1 min
Nové Ouholice
08:25≈ on time ≈ +1 min
Nelahozeves
08:28≈ on time ≈ +1 min
Nelahozeves zámek
08:31≈ on time ≈ +1 min
Kralupy n.V.
08:36on 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
Thu 5 NovKralupy n.V. 08:390 min+1 min
Wed 4 NovKralupy n.V. 08:390 min+1 min
Tue 3 NovKralupy n.V. 08:39+2 min+2 min
Mon 2 NovKralupy n.V. 08:39−1 min—
Fri 30 OctKralupy n.V. 08:37No data—
Thu 29 OctKralupy n.V. 08:42+1 min+1 min
Tue 27 OctKralupy n.V. 08:39−1 min—
Mon 26 OctKralupy n.V. 08:370 min+1 min
Fri 23 OctKralupy n.V. 08:370 min—
Thu 22 OctKralupy n.V. 08:42+3 min+3 min
Wed 21 OctKralupy n.V. 08:39−1 min—
Tue 20 OctKralupy n.V. 08:41+1 min+2 min
Mon 19 OctKralupy n.V. 08:400 min+1 min
Fri 16 OctKralupy n.V. 08:400 min+2 min
Thu 15 OctKralupy n.V. 08:44+4 min+4 min
Wed 14 OctKralupy n.V. 08:40−1 min+1 min
Tue 13 OctKralupy n.V. 08:41+1 min+2 min
Mon 12 OctKralupy n.V. 08:40+2 min+2 min
Fri 9 OctKralupy n.V. 08:39−1 min—
Thu 8 OctKralupy n.V. 08:390 min+1 min
Wed 7 OctKralupy n.V. 08:40+1 min+1 min
Tue 6 OctKralupy n.V. 08:40+1 min+1 min
Mon 5 Oct— 08:500 min+1 min
Fri 2 Oct— 08:50−1 min+1 min
Thu 1 Oct— 08:52+2 min+3 min
Wed 30 Sept— 08:49−1 min—
Tue 29 Sept— 08:52+1 min+1 min
Fri 25 Sept— 08:48−2 min—
Thu 24 Sept— 08:49−2 min—
Wed 23 Sept— 08:500 min—