Train NS 8156 Hoofddorp – Amsterdam Centraal

Hoofddorp 17:02 → Amsterdam Centraal 17:25 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:02 from Hoofddorp · Thu 5 Nov

Next departure 17:02 today · Hoofddorp
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 1 full · 9 partial · 17 no data
On-time · 90 days
82%
9/11 runs under 3 min
RT coverage: 1 full · 10 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+7min
9 in 10 runs arrive with less than this
30 days: +2 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 7 Oct Max en route +8 min · last fix heading to Amsterdam Sloterdijk +8 min
  • Tue 6 Oct Max en route +7 min · last fix heading to Amsterdam Sloterdijk +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 9
  • 3–10 min 18% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 11 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
17:02on time on time
17:07 / 17:09— —
17:15— —
17:19— —
17:25— —

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 4 NovAmsterdam Sloterdijk 17:33No data—
Tue 3 NovAmsterdam Sloterdijk 17:33No data—
Mon 2 NovAmsterdam Sloterdijk 17:33No data—
Sun 1 NovAmsterdam Sloterdijk 17:34Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 17:33Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 17:33No data—
Thu 29 OctAmsterdam Sloterdijk 17:33No data—
Wed 28 OctAmsterdam Sloterdijk 17:33No data—
Tue 27 OctAmsterdam Sloterdijk 17:33No data—
Mon 26 OctAmsterdam Sloterdijk 17:33No data—
Sun 25 OctAmsterdam Sloterdijk 17:35No data—
Sat 24 OctAmsterdam Sloterdijk 17:33Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 17:35No data—
Thu 22 OctAmsterdam Sloterdijk 17:33No data—
Wed 21 OctAmsterdam Sloterdijk 17:34No data—
Tue 20 OctAmsterdam Sloterdijk 17:34Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 17:34No data—
Sun 18 OctAmsterdam Sloterdijk 17:33Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 17:34Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 17:33No data—
Thu 15 OctAmsterdam Sloterdijk 17:33No data—
Wed 14 OctAmsterdam Sloterdijk 17:33No data—
Tue 13 OctAmsterdam Sloterdijk 17:33No data—
Mon 12 OctAmsterdam Sloterdijk 17:33Partial coverage0 min—
Fri 9 OctAmsterdam Sloterdijk 17:33Partial coverage+1 min+1 min
Thu 8 OctAmsterdam Sloterdijk 17:340 min—
Wed 7 OctAmsterdam Sloterdijk 17:33Partial coverage+8 min+8 min
Tue 6 OctAmsterdam Sloterdijk 17:33Partial coverage+7 min+7 min
Fri 2 OctAmsterdam Sloterdijk 17:33No data—
Thu 1 OctAmsterdam Sloterdijk 17:33No data—