Train NS 5730 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 10:11 → Leiden Centraal 11:40 Daily 1 h 29 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sassenheim at 11:49 No data

  1. Utrecht Centraal10:11
  2. Hilversum Sportpark10:27
  3. Bussum Zuid10:37
  4. Diemen Zuid11:00
  5. Amsterdam RAI11:06
  6. Sassenheim11:35
  7. Leiden Centraal11:40

Next service: tomorrow 10:11 from Utrecht Centraal · Sat 7 Nov

Next departure 10:11 tomorrow · Utrecht Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 9 full · 7 partial · 12 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 9 full · 9 partial · 67 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 Leiden Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sun 1 Nov Max en route +4 min · last fix heading to Hilversum Sportpark +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 50% S n=2

Stops and timetable

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

Last 90 days, 18 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
10:11on time on time
10:15≈ on time ≈ +1 min
10:23≈ on time ≈ +1 min
10:27≈ on time ≈ +1 min
10:30 / 10:31≈ on time ≈ +1 min
10:33≈ on time ≈ +1 min
10:37≈ on time ≈ +1 min
10:40≈ on time ≈ +1 min
10:46 / 10:53≈ on time ≈ +1 min
11:00≈ on time ≈ +2 min
11:02≈ on time ≈ +2 min
11:06≈ on time ≈ +2 min
11:09 / 11:10≈ on time ≈ +2 min
11:16 / 11:19≈ on time ≈ +2 min
11:23≈ on time ≈ +2 min
11:28≈ on time ≈ +2 min
11:35≈ on time ≈ +2 min
11:40on 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
Fri 6 NovSassenheim 11:49No data—
Thu 5 NovSassenheim 11:49No data—
Wed 4 NovSassenheim 11:49Partial coverage0 min—
Tue 3 NovSassenheim 11:49No data—
Mon 2 NovSassenheim 11:49Partial coverage0 min—
Sun 1 NovHilversum Sportpark 10:42+3 min+4 min
Sat 31 OctSchiphol Airport 11:320 min—
Fri 30 OctSassenheim 11:49No data—
Thu 29 OctSassenheim 11:56Partial coverage0 min—
Wed 28 OctSassenheim 11:49No data—
Tue 27 OctSassenheim 11:49No data—
Mon 26 OctSassenheim 11:49Partial coverage0 min—
Sun 25 OctSchiphol Airport 11:32No data—
Sat 24 OctSchiphol Airport 11:34+2 min+3 min
Fri 23 OctSassenheim 11:480 min—
Thu 22 OctSassenheim 11:49No data—
Wed 21 OctAmsterdam Zuid 11:24No data—
Tue 20 OctSassenheim 11:49Partial coverage0 min—
Mon 19 OctSassenheim 11:490 min—
Fri 16 OctSassenheim 11:480 min—
Thu 15 OctSassenheim 11:50No data—
Wed 14 OctSassenheim 11:51No data—
Tue 13 OctSassenheim 11:50No data—
Mon 12 OctSassenheim 11:49Partial coverage0 min—
Sun 11 OctBussum Zuid 13:220 min—
Sat 10 OctSchiphol Airport 11:320 min—
Fri 9 OctSassenheim 11:490 min—
Thu 8 OctSassenheim 11:49Partial coverage0 min—
Wed 7 OctHoofddorp 12:01Partial coverage0 min—
Tue 6 OctSassenheim 11:49Partial coverage0 min—