Train NS 5720 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 07:41 → Leiden Centraal 09:09 Mon, Tue, Wed, Thu, Fri 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: tomorrow 07:41 from Utrecht Centraal · Mon 9 Nov

Next departure 07:41 tomorrow · Utrecht Centraal
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 1 full · 9 partial · 10 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 2 full · 12 partial · 57 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

  • Wed 4 Nov Max en route +14 min · last fix heading to Sassenheim +12 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 0% · 0
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
07:41on time on time
07:45— —
07:53— —
07:57— —
08:00 / 08:01— —
08:03— —
08:07— —
08:10— —
08:16 / 08:23— —
08:30— —
08:32— —
08:36— —
08:39 / 08:40— —
08:46 / 08:48— —
08:53— —
08:57— —
09:04— —
09:09— —

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 09:18No data—
Thu 5 NovSassenheim 09:18No data—
Wed 4 NovSassenheim 09:33Partial coverage+12 min+14 min
Tue 3 NovSassenheim 09:19No data—
Mon 2 NovSassenheim 09:19Partial coverage0 min—
Fri 30 OctSassenheim 09:19No data—
Thu 29 OctSassenheim 09:18Partial coverage0 min—
Wed 28 OctSassenheim 09:19No data—
Tue 27 OctSassenheim 09:19Partial coverage0 min—
Mon 26 OctSassenheim 09:19Partial coverage0 min—
Fri 23 OctSassenheim 09:190 min—
Thu 22 OctSassenheim 09:18Partial coverage0 min—
Wed 21 OctSassenheim 09:19No data—
Tue 20 OctSassenheim 09:19Partial coverage0 min—
Mon 19 OctSassenheim 09:19Partial coverage0 min—
Fri 16 OctSassenheim 09:18No data—
Thu 15 OctSassenheim 09:19No data—
Wed 14 OctSassenheim 09:22No data—
Tue 13 OctSassenheim 09:19No data—
Mon 12 OctSassenheim 09:20Partial coverage0 min—
Fri 9 OctSassenheim 09:21+2 min+2 min
Thu 8 OctSassenheim 09:19Partial coverage0 min—
Wed 7 OctSassenheim 09:20Partial coverage+2 min+2 min
Tue 6 OctSassenheim 09:19Partial coverage0 min—
Mon 5 OctSassenheim 09:19No data—
Fri 2 OctSassenheim 09:18No data—
Thu 1 OctSassenheim 09:19No data—
Wed 30 SeptSassenheim 09:19No data—
Tue 29 SeptSassenheim 09:29No data—
Mon 28 SeptSassenheim 09:20No data—