Train NS 8162 Hoofddorp – Amsterdam Centraal

Hoofddorp 18:32 → Amsterdam Centraal 18:55 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:32 from Hoofddorp · Sat 7 Nov

Next departure 18:32 today · Hoofddorp
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 3 full · 9 partial · 15 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 6 full · 9 partial · 34 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 28 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=3
  • 50% W n=2
  • 100% T n=2
  • 100% F n=3
  • 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, 15 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
18:32on time on time
18:37 / 18:39≈ on time ≈ +1 min
18:45≈ on time ≈ +1 min
18:49≈ on time ≈ +2 min
18:55on time +2 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
Fri 6 NovAmsterdam Lelylaan 18:59Partial coverage0 min+1 min
Thu 5 Nov— 18:54No data—
Wed 4 Nov— 18:54No data—
Tue 3 Nov— 18:59No data—
Mon 2 NovHoofddorp 18:54Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 19:03Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 19:03Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 19:03No data—
Thu 29 Oct— 18:57+1 min+1 min
Wed 28 Oct— 19:06+4 min+5 min
Tue 27 Oct— 18:570 min—
Mon 26 Oct— 18:56No data—
Sun 25 OctAmsterdam Sloterdijk 19:04No data—
Sat 24 OctAmsterdam Sloterdijk 19:03Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 19:03Partial coverage0 min—
Thu 22 OctAmsterdam Lelylaan 18:59No data—
Wed 21 OctSchiphol Airport 19:07No data—
Tue 20 OctAmsterdam Lelylaan 18:50Partial coverage0 min—
Mon 19 OctSchiphol Airport 18:57No data—
Sun 18 OctAmsterdam Sloterdijk 19:04Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 19:03No data—
Fri 16 OctAmsterdam Sloterdijk 19:03No data—
Thu 15 Oct— 18:58No data—
Wed 14 OctAmsterdam Sloterdijk 19:03No data—
Tue 13 OctSchiphol Airport 18:57No data—
Mon 12 OctAmsterdam Lelylaan 18:59No data—
Fri 9 OctHoofddorp 18:57Partial coverage0 min+1 min
Thu 8 Oct— 18:560 min+1 min
Wed 7 Oct— 18:560 min—
Tue 6 Oct— 18:560 min—