Train NS 5751 Hoofddorp – Utrecht Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 14:07 from Hoofddorp · Sun 8 Nov

Next departure 14:07 today · Hoofddorp
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 9 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 19 full · 4 partial · 61 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: 0 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

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=3
  • 100% T n=5
  • 100% W n=3
  • 100% T n=2
  • 100% F n=4
  • 100% S n=4
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 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
14:07on time on time
14:11 / 14:13≈ on time ≈ on time
14:19 / 14:20≈ on time ≈ on time
14:22≈ on time ≈ on time
14:25 / 14:26≈ on time ≈ on time
14:29≈ on time ≈ on time
14:35 / 14:43≈ on time ≈ on time
14:49≈ on time ≈ on time
14:52≈ on time ≈ on time
14:56≈ on time ≈ on time
14:58 / 14:59≈ on time ≈ on time
15:02≈ on time ≈ on time
15:06≈ on time ≈ on time
15:14≈ on time ≈ on time
15:18on time on time

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 NovUtrecht Overvecht 15:28Partial coverage0 min—
Fri 6 NovUtrecht Overvecht 15:28No data—
Thu 5 NovUtrecht Overvecht 15:28No data—
Wed 4 NovUtrecht Overvecht 15:280 min—
Tue 3 NovUtrecht Overvecht 15:280 min—
Mon 2 NovUtrecht Overvecht 15:280 min—
Sun 1 NovUtrecht Overvecht 15:28Partial coverage0 min—
Sat 31 OctUtrecht Overvecht 15:29Partial coverage+1 min+1 min
Fri 30 OctUtrecht Overvecht 15:280 min—
Thu 29 OctUtrecht Overvecht 15:280 min—
Wed 28 OctUtrecht Overvecht 15:280 min—
Tue 27 OctUtrecht Overvecht 15:280 min—
Mon 26 OctUtrecht Overvecht 15:28No data—
Sun 25 OctUtrecht Overvecht 15:32No data—
Sat 24 OctUtrecht Overvecht 15:300 min—
Fri 23 OctUtrecht Overvecht 15:310 min—
Thu 22 OctUtrecht Overvecht 15:28No data—
Wed 21 OctUtrecht Overvecht 15:29No data—
Tue 20 OctUtrecht Overvecht 15:280 min—
Mon 19 OctUtrecht Overvecht 15:300 min—
Fri 16 OctUtrecht Overvecht 15:290 min—
Thu 15 OctUtrecht Overvecht 15:29No data—
Wed 14 OctUtrecht Overvecht 15:33No data—
Tue 13 OctUtrecht Overvecht 15:280 min—
Mon 12 OctUtrecht Overvecht 15:28No data—
Sun 11 OctUtrecht Overvecht 15:29+1 min+2 min
Sat 10 OctUtrecht Overvecht 15:28Partial coverage0 min—
Fri 9 OctUtrecht Overvecht 15:280 min—
Thu 8 OctUtrecht Overvecht 15:280 min—
Wed 7 OctUtrecht Overvecht 15:29+1 min+1 min