Train NS 5775 Hoofddorp – Utrecht Centraal

Hoofddorp 20:07 → Utrecht Centraal 21:18 Daily 1 h 11 min · 15 stops NS (Nederlandse Spoorwegen)

Running now · updated 20:35

Heading to Utrecht Centraal 0 min

Estimated arrival at Utrecht Centraal 21:18 · 52 km/h

  1. Hoofddorp20:07
  2. Amsterdam Zuid20:19
  3. Diemen Zuid20:30
  4. Naarden-Bussum20:49
  5. Hilversum Media Park20:56
  6. Hollandsche Rading21:06
  7. Utrecht Centraal21:18

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

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

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

  • Early 0% · 0
  • On time 100% · 7
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • 100% W n=1
  • 100% T n=1
  • 100% F n=1
  • 100% S n=1
  • 100% S n=1

Stops and timetable

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

StopSched.Today
Hoofddorp
20:07
Schiphol Airport
20:11 / 20:13
Amsterdam Zuid
20:19 / 20:20
Amsterdam RAI
20:22
Duivendrecht
20:25 / 20:27
Diemen Zuid
20:30
Weesp
20:36 / 20:43
Naarden-Bussum
20:49
Bussum Zuid
20:52
Hilversum Media Park
20:56
Hilversum
20:58 / 20:59
Hilversum Sportpark
21:02
Hollandsche Rading
21:06
Utrecht Overvecht
21:14
Utrecht Centraal
21: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
Sun 11 OctWeesp 20:34Partial coverage0 min—
Sat 10 OctUtrecht Overvecht 21:280 min+2 min
Fri 9 Oct— 21:20+1 min+1 min
Thu 8 Oct— 21:200 min+1 min
Wed 7 Oct— 21:190 min—
Tue 6 Oct— 21:190 min—
Mon 5 Oct— 21:200 min+2 min
Sun 4 OctUtrecht Overvecht 21:28No data—
Sat 3 OctUtrecht Overvecht 21:28No data—
Sun 27 SeptUtrecht Overvecht 21:31No data—
Sat 26 SeptUtrecht Overvecht 21:27No data—
Sun 20 SeptUtrecht Overvecht 21:31No data—
Sat 19 SeptUtrecht Overvecht 21:30No data—
Sun 13 SeptUtrecht Overvecht 21:23No data—
Sat 12 SeptUtrecht Overvecht 21:23No data—
Sun 6 SeptUtrecht Overvecht 21:28No data—
Sat 5 SeptUtrecht Overvecht 21:28No data—
Sun 30 AugDiemen Zuid 20:44No data—
Sat 29 AugDiemen Zuid 20:44No data—
Fri 21 AugDiemen Zuid 20:43No data—
Sun 16 AugUtrecht Overvecht 21:28No data—
Sat 15 AugUtrecht Overvecht 21:37No data—
Fri 14 AugWeesp 20:57No data—
Wed 12 AugDiemen 20:48No data—
Sun 9 AugUtrecht Overvecht 21:28No data—
Sat 8 AugUtrecht Overvecht 21:28No data—
Fri 7 AugUtrecht Overvecht 21:28No data—
Sun 2 AugUtrecht Overvecht 21:31No data—
Sat 1 AugUtrecht Overvecht 21:30No data—
Fri 31 JulDiemen Zuid 20:43No data—