Train NS 5750 Utrecht Centraal – Leiden Centraal

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

✓ Today’s run finished

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

  1. Utrecht Centraal15:11
  2. Hilversum Sportpark15:27
  3. Bussum Zuid15:37
  4. Diemen Zuid16:00
  5. Amsterdam RAI16:06
  6. Sassenheim16:35
  7. Leiden Centraal16:40

Next service: tomorrow 15:11 from Utrecht Centraal · Fri 6 Nov

Next departure 15:11 tomorrow · Utrecht Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 8 full · 10 partial · 10 no data
On-time · 90 days
100%
20/20 runs under 3 min
RT coverage: 9 full · 11 partial · 65 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: 0 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=4
  • 100% T n=2
  • 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
15:11on time on time
15:15≈ on time ≈ on time
15:23≈ on time ≈ on time
15:27≈ on time ≈ on time
15:30 / 15:31≈ on time ≈ on time
15:33≈ on time ≈ on time
15:37≈ on time ≈ on time
15:40≈ on time ≈ on time
15:46 / 15:53≈ on time ≈ on time
16:00≈ on time ≈ on time
16:02≈ on time ≈ on time
16:06≈ on time ≈ on time
16:09 / 16:10≈ on time ≈ on time
16:16 / 16:19≈ on time ≈ on time
16:23≈ on time ≈ on time
16:28≈ on time ≈ on time
16:35≈ on time ≈ on time
16:40on 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
Thu 5 NovSassenheim 16:49No data—
Wed 4 NovSassenheim 16:49Partial coverage0 min—
Tue 3 NovSassenheim 16:49No data—
Mon 2 NovSassenheim 16:49Partial coverage0 min—
Sun 1 NovSchiphol Airport 16:330 min—
Sat 31 OctSchiphol Airport 16:320 min—
Fri 30 OctSassenheim 16:48No data—
Thu 29 OctSassenheim 16:49Partial coverage0 min—
Wed 28 OctSassenheim 16:48No data—
Tue 27 OctSassenheim 16:49No data—
Mon 26 OctSassenheim 16:49No data—
Sun 25 OctSchiphol Airport 16:32No data—
Sat 24 OctSchiphol Airport 16:320 min—
Fri 23 OctSassenheim 16:480 min—
Thu 22 OctSassenheim 16:51Partial coverage0 min—
Wed 21 OctSassenheim 17:09No data—
Tue 20 OctSassenheim 16:49Partial coverage0 min—
Mon 19 OctSassenheim 16:50Partial coverage0 min—
Fri 16 OctSassenheim 16:490 min—
Thu 15 OctSassenheim 16:49No data—
Wed 14 OctSassenheim 16:49Partial coverage0 min—
Tue 13 OctSassenheim 16:49No data—
Mon 12 OctSassenheim 16:49Partial coverage0 min—
Sun 11 OctSchiphol Airport 16:320 min—
Sat 10 OctSchiphol Airport 16:320 min—
Fri 9 OctSassenheim 16:480 min—
Thu 8 OctSassenheim 16:49Partial coverage0 min—
Wed 7 OctSassenheim 16:49Partial coverage0 min—
Tue 6 OctSassenheim 16:50Partial coverage+1 min+1 min
Mon 5 OctSassenheim 16:480 min—