Train NS 5758 Utrecht Centraal – Leiden Centraal

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 17:11 from Utrecht Centraal · Fri 6 Nov

Next departure 17:11 today · Utrecht Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 10 full · 8 partial · 9 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 11 full · 10 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sat 10 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min
  • Sun 11 Oct Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=4
  • 67% 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, 21 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
17:11on time on time
17:15≈ on time ≈ on time
17:23≈ on time ≈ on time
17:27≈ on time ≈ +1 min
17:30 / 17:31≈ on time ≈ +1 min
17:33≈ on time ≈ +1 min
17:37≈ on time ≈ +1 min
17:40≈ on time ≈ +1 min
17:46 / 17:53≈ on time ≈ +1 min
18:00≈ on time ≈ +2 min
18:02≈ on time ≈ +2 min
18:06≈ on time ≈ +2 min
18:09 / 18:10≈ on time ≈ +2 min
18:16 / 18:19≈ on time ≈ +2 min
18:23≈ on time ≈ +2 min
18:28≈ on time ≈ +3 min
18:35≈ on time ≈ +3 min
18:40on time +3 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 NovHollandsche Rading 18:39No data—
Wed 4 NovAmsterdam Zuid 18:39No data—
Tue 3 NovAmsterdam Zuid 18:39No data—
Mon 2 NovAmsterdam Zuid 18:39Partial coverage0 min—
Sun 1 NovSchiphol Airport 18:320 min—
Sat 31 OctSchiphol Airport 18:320 min—
Fri 30 OctSassenheim 18:480 min—
Thu 29 OctDuivendrecht 19:17Partial coverage0 min—
Wed 28 OctUtrecht Centraal 18:42Partial coverage0 min—
Tue 27 OctDuivendrecht 18:46No data—
Mon 26 OctAmsterdam RAI 18:41Partial coverage0 min—
Sun 25 OctSchiphol Airport 18:32No data—
Sat 24 OctSchiphol Airport 18:320 min—
Fri 23 OctSassenheim 18:480 min—
Thu 22 OctSassenheim 18:49No data—
Wed 21 OctSassenheim 18:49No data—
Tue 20 OctSassenheim 18:49Partial coverage0 min—
Mon 19 OctSassenheim 18:49Partial coverage0 min—
Fri 16 OctSassenheim 18:540 min—
Thu 15 OctNieuw Vennep 18:47No data—
Wed 14 OctSassenheim 18:52No data—
Tue 13 OctSassenheim 18:49Partial coverage0 min—
Mon 12 OctSassenheim 18:490 min—
Sun 11 OctSchiphol Airport 18:33+3 min+3 min
Sat 10 OctSchiphol Airport 18:35+4 min+4 min
Fri 9 OctSassenheim 18:480 min—
Thu 8 OctDuivendrecht 18:42Partial coverage0 min—
Wed 7 OctWeesp 18:45Partial coverage+2 min+2 min
Tue 6 OctDuivendrecht 18:41Partial coverage0 min—
Mon 5 OctAmsterdam Zuid 18:45+2 min+2 min