Train NS 5766 Utrecht Centraal – Hoofddorp

Utrecht Centraal 19:11 → Hoofddorp 20:22 Daily 1 h 11 min · 15 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Saturday 7 November +2 min

Next service: tomorrow 19:11 from Utrecht Centraal · Mon 9 Nov

Next departure 19:11 tomorrow · Utrecht Centraal
On-time · 30 days
86%
12/14 runs under 3 min
RT coverage: 9 full · 5 partial · 11 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 35 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Hoofddorp, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 29 Oct Max en route +5 min · last fix heading to — +5 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
19:11on time on time
19:15≈ on time ≈ on time
19:23≈ on time ≈ on time
19:27≈ on time ≈ +1 min
19:30 / 19:31≈ on time ≈ +1 min
19:33≈ on time ≈ +1 min
19:37≈ on time ≈ +1 min
19:40≈ on time ≈ +1 min
19:46 / 19:53≈ on time ≈ +1 min
20:00≈ on time ≈ +2 min
20:02≈ on time ≈ +2 min
20:06≈ on time ≈ +2 min
20:09 / 20:10≈ on time ≈ +2 min
20:16 / 20:18≈ on time ≈ +3 min
20:22on 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
Sat 7 NovSchiphol Airport 20:32Partial coverage+2 min+2 min
Fri 6 Nov— 20:230 min—
Thu 5 Nov— 20:24No data—
Wed 4 Nov— 20:240 min—
Sun 1 NovSchiphol Airport 20:32Partial coverage0 min—
Sat 31 OctSchiphol Airport 20:32Partial coverage0 min—
Fri 30 Oct— 20:26No data—
Thu 29 Oct— 20:23+5 min+5 min
Wed 28 Oct— 19:41No data—
Tue 27 Oct— 20:240 min—
Mon 26 OctWeesp 20:24No data—
Sun 25 OctSchiphol Airport 20:32No data—
Sat 24 OctSchiphol Airport 20:440 min—
Fri 23 OctHilversum Sportpark 20:23Partial coverage0 min—
Thu 22 Oct— 20:24No data—
Wed 21 Oct— 20:35No data—
Tue 20 Oct— 20:23No data—
Mon 19 Oct— 20:380 min—
Fri 16 OctWeesp 20:32No data—
Thu 15 Oct— 20:26No data—
Wed 14 OctNaarden-Bussum 20:23No data—
Tue 13 Oct— 20:230 min—
Mon 12 Oct— 20:230 min—
Sun 11 OctSchiphol Airport 20:36+4 min+5 min
Sat 10 OctSchiphol Airport 20:32Partial coverage0 min—
Fri 9 Oct— 20:110 min—
Thu 8 Oct— 02:250 min—
Wed 7 Oct— 02:280 min—
Tue 6 Oct— 20:230 min—
Mon 5 Oct— 20:230 min—