Train NS 5710 Utrecht Centraal – Leiden Centraal

Utrecht Centraal 05:07 → Leiden Centraal 06:29 Mon, Tue, Wed, Thu, Fri 1 h 22 min · 17 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Sassenheim at 06:54 0 min

  1. Utrecht Centraal05:07
  2. Hilversum05:23
  3. Bussum Zuid05:30
  4. Diemen Zuid05:48
  5. Amsterdam Zuid05:57
  6. Sassenheim06:23
  7. Leiden Centraal06:29

Next service: tomorrow 05:07 from Utrecht Centraal · Fri 6 Nov

Next departure 05:07 tomorrow · Utrecht Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 17 full · 5 partial · 0 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 18 full · 5 partial · 41 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

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

  • Early 0% · 0
  • On time 100% · 23
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
05:07on time on time
05:11≈ on time ≈ on time
05:20≈ on time ≈ on time
05:23 / 05:24≈ on time ≈ on time
05:26≈ on time ≈ on time
05:30≈ on time ≈ on time
05:33≈ on time ≈ on time
05:39 / 05:41≈ on time ≈ on time
05:48≈ on time ≈ on time
05:50≈ on time ≈ on time
05:55≈ on time ≈ on time
05:57 / 06:00≈ on time ≈ on time
06:06 / 06:08≈ on time ≈ +1 min
06:12≈ on time ≈ +1 min
06:17≈ on time ≈ +1 min
06:23≈ on time ≈ +1 min
06:29on time +1 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 NovSassenheim 06:54Partial coverage0 min—
Wed 4 NovSassenheim 06:54+1 min—
Tue 3 NovSassenheim 06:38Partial coverage0 min—
Mon 2 NovSassenheim 06:490 min—
Fri 30 OctSassenheim 06:55+1 min—
Thu 29 OctSchiphol Airport 06:22Partial coverage0 min—
Wed 28 OctUtrecht Centraal 06:520 min—
Tue 27 OctSassenheim 06:520 min—
Mon 26 OctSassenheim 06:51+1 min—
Fri 23 OctSassenheim 06:55+1 min—
Thu 22 OctSassenheim 06:510 min—
Wed 21 OctSassenheim 06:510 min—
Tue 20 OctSassenheim 06:390 min—
Mon 19 OctSassenheim 06:51+1 min—
Fri 16 OctSassenheim 06:54+1 min—
Thu 15 OctSassenheim 06:51Partial coverage0 min—
Wed 14 OctSassenheim 06:510 min—
Tue 13 OctSassenheim 06:38+1 min—
Mon 12 OctSassenheim 06:520 min—
Fri 9 OctSassenheim 06:540 min—
Thu 8 OctSassenheim 06:52Partial coverage+1 min—
Wed 7 OctSassenheim 06:510 min—
Tue 6 OctSassenheim 06:51+1 min—
Mon 5 OctSassenheim 06:42No data—
Fri 2 OctSassenheim 06:38No data—
Thu 1 OctSassenheim 06:38No data—
Wed 30 SeptSassenheim 06:39No data—
Tue 29 SeptSassenheim 06:38No data—
Mon 28 SeptSassenheim 06:38No data—
Sat 26 SeptHilversum Sportpark 05:44No data—