Train NS 5734 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 11:11 → Leiden Centraal 12:39 Daily 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Utrecht Centraal11:11
  2. Hilversum Sportpark11:27
  3. Bussum Zuid11:37
  4. Diemen Zuid12:00
  5. Amsterdam RAI12:06
  6. Sassenheim12:34
  7. Leiden Centraal12:39

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

Next departure 11:11 tomorrow · Utrecht Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 9 full · 8 partial · 11 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 10 full · 10 partial · 65 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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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