Train NS 5759 Leiden Centraal – Utrecht Centraal

Leiden Centraal 15:50 → Utrecht Centraal 17:18 Daily 1 h 28 min · 18 stops NS (Nederlandse Spoorwegen)

Running now · updated 16:05

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 17:18 · 101 km/h

  1. Leiden Centraal15:50
  2. Hoofddorp16:07
  3. Amsterdam RAI16:22
  4. Weesp16:35
  5. Bussum Zuid16:52
  6. Hilversum Sportpark17:02
  7. Utrecht Centraal17:18

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 16 runs arrived on time.

Open live map ↗ Full trip card
Open live card ↗
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 12 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 6 full · 10 partial · 69 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 Utrecht 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

StopSched.Today
Leiden Centraal
15:50
Sassenheim
15:55
Nieuw Vennep
16:02
Hoofddorp
16:07
Schiphol Airport
16:11 / 16:13
Amsterdam Zuid
16:19 / 16:20
Amsterdam RAI
16:22
Duivendrecht
16:25 / 16:26
Diemen Zuid
16:29
Weesp
16:35 / 16:43
Naarden-Bussum
16:49
Bussum Zuid
16:52
Hilversum Media Park
16:56
Hilversum
16:58 / 16:59
Hilversum Sportpark
17:02
Hollandsche Rading
17:06
Utrecht Overvecht
17:14
Utrecht Centraal
17:18

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.

Recent runs

DateLast stopFinalMax
Fri 30 OctHoofddorp 16:04Partial coverage0 min—
Thu 29 OctUtrecht Overvecht 17:28Partial coverage0 min—
Wed 28 OctUtrecht Overvecht 17:28Partial coverage0 min—
Tue 27 OctUtrecht Overvecht 17:28No data—
Mon 26 OctUtrecht Overvecht 17:28No data—
Sun 25 OctUtrecht Overvecht 17:30No data—
Sat 24 OctUtrecht Overvecht 17:290 min—
Fri 23 OctUtrecht Overvecht 17:30No data—
Thu 22 OctUtrecht Overvecht 17:28Partial coverage0 min—
Wed 21 OctUtrecht Overvecht 17:290 min—
Tue 20 OctUtrecht Overvecht 17:34No data—
Mon 19 OctLeiden Centraal 17:38Partial coverage0 min—
Fri 16 OctUtrecht Overvecht 17:28No data—
Thu 15 OctUtrecht Overvecht 17:31No data—
Wed 14 OctUtrecht Overvecht 17:28No data—
Tue 13 OctUtrecht Overvecht 17:28Partial coverage0 min—
Mon 12 OctUtrecht Overvecht 17:29Partial coverage0 min—
Sun 11 OctUtrecht Overvecht 17:280 min—
Sat 10 OctUtrecht Overvecht 17:280 min—
Fri 9 OctUtrecht Overvecht 17:29Partial coverage0 min—
Thu 8 OctUtrecht Overvecht 17:28+1 min+1 min
Wed 7 OctUtrecht Overvecht 17:28Partial coverage+1 min+1 min
Tue 6 OctUtrecht Overvecht 17:28Partial coverage0 min—
Mon 5 OctUtrecht Overvecht 17:270 min—
Sun 4 OctUtrecht Overvecht 17:28No data—
Sat 3 OctUtrecht Overvecht 17:28No data—
Fri 2 OctUtrecht Overvecht 17:30No data—
Thu 1 OctUtrecht Overvecht 17:28No data—
Wed 30 SeptUtrecht Overvecht 17:28No data—
Tue 29 SeptUtrecht Overvecht 17:28No data—