Os 9733 9733 Slaný – Kralupy n.V.

View line Os 9733

Slaný 12:34 → Kralupy n.V. 13:04 Daily 0 h 30 min · 10 stops České dráhy, a.s.

✓ Today’s run finished

Today it reached Kralupy n.V. at 13:06 +2 min

  1. Slaný12:34
  2. Podlešín12:42
  3. Zvoleněves12:46
  4. Neuměřice12:51
  5. Olovnice12:55
  6. Kralupy nad Vltavou předměstí13:00
  7. Kralupy n.V.13:04

Next service: tomorrow 12:34 from Slaný · Sun 8 Nov

Next departure 12:34 tomorrow · Slaný
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
88/90 runs under 3 min
RT coverage: 90 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Wed 21 Oct Max en route +4 min · last fix heading to Kralupy n.V. +4 min
  • Thu 20 Aug Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 88
  • 3–10 min 2% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=13
  • 100% T n=13
  • 92% W n=13
  • 92% T n=13
  • 100% F n=13
  • 100% S n=13
  • 100% S n=12

Stops and timetable

Timetable of the latest run from the operator’s GTFS (10 stops).

Last 90 days, 90 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
12:34on time +1 min
12:38≈ on time ≈ +1 min
12:42 / 12:43≈ on time ≈ +1 min
12:46 / 12:47≈ on time ≈ +1 min
12:49≈ on time ≈ +1 min
12:51≈ on time ≈ +1 min
12:55≈ on time ≈ +1 min
12:58≈ on time ≈ +2 min
13:00 / 13:01≈ on time ≈ +2 min
13:04on time +2 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
Sat 7 NovKralupy n.V. 13:09+2 min+3 min
Fri 6 NovKralupy n.V. 13:09+1 min+1 min
Thu 5 NovKralupy n.V. 13:080 min+1 min
Wed 4 NovKralupy n.V. 13:09+1 min+1 min
Tue 3 NovKralupy n.V. 13:09+1 min+2 min
Mon 2 NovKralupy n.V. 13:09+2 min+2 min
Sun 1 NovKralupy n.V. 13:09+1 min+1 min
Sat 31 OctKralupy n.V. 13:100 min—
Fri 30 OctKralupy n.V. 13:090 min+1 min
Thu 29 OctKralupy n.V. 13:10+1 min+2 min
Wed 28 OctKralupy n.V. 13:06+1 min+1 min
Tue 27 OctKralupy n.V. 13:06+1 min+1 min
Mon 26 OctKralupy n.V. 13:09+1 min+1 min
Sun 25 OctKralupy n.V. 13:10+1 min+1 min
Sat 24 OctKralupy n.V. 13:060 min+1 min
Fri 23 OctKralupy n.V. 13:080 min+1 min
Thu 22 OctKralupy n.V. 13:080 min—
Wed 21 OctKralupy n.V. 13:09+4 min+4 min
Tue 20 OctKralupy n.V. 13:060 min+1 min
Mon 19 OctKralupy n.V. 13:06+1 min+1 min
Sun 18 OctKralupy n.V. 13:10+1 min+1 min
Sat 17 OctKralupy n.V. 13:10+2 min+2 min
Fri 16 OctKralupy n.V. 13:090 min+1 min
Thu 15 OctKralupy n.V. 13:10+2 min+2 min
Wed 14 OctKralupy n.V. 13:09+1 min+1 min
Tue 13 OctKralupy n.V. 13:10+2 min+2 min
Mon 12 OctKralupy n.V. 13:080 min+1 min
Sun 11 OctKralupy n.V. 13:090 min+3 min
Sat 10 OctKralupy n.V. 13:060 min+1 min
Fri 9 OctKralupy n.V. 13:09+1 min+1 min