Train NS 8166 Hoofddorp – Amsterdam Centraal

Hoofddorp 19:32 → Amsterdam Centraal 19:55 Mon, Tue, Wed, Thu, Fri 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 18 November 0 min

Next service: today 19:32 from Hoofddorp · Thu 19 Nov

Next departure 19:32 today · Hoofddorp
On-time · 30 days
82%
14/17 runs under 3 min
RT coverage: 15 full · 2 partial · 10 no data
On-time · 90 days
87%
20/23 runs under 3 min
RT coverage: 20 full · 3 partial · 23 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: +4 min

Last 30 days

Arrival delay at Amsterdam Centraal, in minutes. One bar per run.

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

Worst days

  • Mon 16 Nov Max en route +7 min · last fix heading to — +6 min
  • Mon 9 Nov Max en route +4 min · last fix heading to — +4 min
  • Thu 29 Oct Max en route +4 min · last fix heading to — +4 min

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 87% · 20
  • 3–10 min 13% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 0% M n=2
  • 100% T n=5
  • 100% W n=5
  • 67% T n=3
  • 100% F n=4
  • 100% S n=2
  • 100% S n=2

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
19:32on time +1 min
19:37 / 19:39≈ on time ≈ +1 min
19:45≈ on time ≈ +3 min
19:49≈ on time ≈ +3 min
19:55on time +4 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
Wed 18 Nov— 19:590 min+1 min
Tue 17 Nov— 19:59+1 min+2 min
Mon 16 Nov— 20:03+6 min+7 min
Fri 13 Nov— 19:57+1 min+1 min
Thu 12 Nov— 19:540 min—
Wed 11 Nov— 19:59+3 min+3 min
Tue 10 Nov— 19:540 min—
Mon 9 Nov— 20:02+4 min+4 min
Sun 8 NovAmsterdam Sloterdijk 20:140 min—
Sat 7 Nov— 19:54No data—
Fri 6 Nov— 19:54+1 min+1 min
Thu 5 Nov— 19:54No data—
Wed 4 Nov— 19:540 min—
Tue 3 Nov— 20:02No data—
Mon 2 Nov— 19:54No data—
Sun 1 NovAmsterdam Sloterdijk 20:03No data—
Sat 31 OctAmsterdam Sloterdijk 20:04Partial coverage0 min+1 min
Fri 30 Oct— 20:00No data—
Thu 29 Oct— 20:02+4 min+4 min
Wed 28 Oct— 20:070 min—
Tue 27 Oct— 20:030 min—
Mon 26 OctAmsterdam Sloterdijk 19:57No data—
Sun 25 OctAmsterdam Sloterdijk 20:05No data—
Sat 24 OctAmsterdam Sloterdijk 20:06Partial coverage0 min—
Fri 23 Oct— 19:560 min—
Thu 22 Oct— 19:57No data—
Wed 21 Oct— 19:57No data—
Tue 20 Oct— 19:570 min—
Mon 19 Oct— 20:01No data—
Sun 18 OctAmsterdam Sloterdijk 20:04Partial coverage0 min+1 min