Train NS 8176 Hoofddorp – Amsterdam Centraal

Hoofddorp 22:03 → Amsterdam Centraal 22:26 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 22:28 No data

  1. Hoofddorp22:03
  2. Schiphol Airport22:07
  3. Amsterdam Lelylaan22:16
  4. Amsterdam Sloterdijk22:19
  5. Amsterdam Centraal22:26

Next service: tomorrow 22:03 from Hoofddorp · Fri 6 Nov

Next departure 22:03 tomorrow · Hoofddorp
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 11 full · 2 partial · 13 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 12 full · 2 partial · 19 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: +1 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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 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=2
  • 100% W n=3
  • 100% T n=2
  • 75% F n=4
  • — S n=0
  • 100% S n=2

Stops and timetable

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

Last 90 days, 14 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
22:03on time on time
22:07 / 22:09≈ on time ≈ on time
22:16≈ on time ≈ on time
22:19≈ on time ≈ +1 min
22:26on time +1 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
Thu 5 Nov— 22:28No data—
Wed 4 Nov— 22:28+1 min—
Tue 3 Nov— 22:28No data—
Sun 1 NovAmsterdam Sloterdijk 22:34Partial coverage+1 min—
Sat 31 OctAmsterdam Sloterdijk 22:34No data—
Fri 30 Oct— 22:270 min—
Wed 28 Oct— 22:27No data—
Tue 27 Oct— 22:27No data—
Mon 26 Oct— 22:27No data—
Sun 25 OctAmsterdam Sloterdijk 22:38No data—
Sat 24 OctAmsterdam Sloterdijk 22:34No data—
Fri 23 Oct— 22:280 min—
Thu 22 Oct— 22:280 min—
Wed 21 Oct— 22:280 min—
Tue 20 Oct— 22:270 min—
Mon 19 Oct— 22:28No data—
Sun 18 OctAmsterdam Sloterdijk 22:34Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 22:34No data—
Fri 16 Oct— 22:290 min+1 min
Thu 15 Oct— 22:33No data—
Wed 14 Oct— 22:32No data—
Tue 13 Oct— 22:28No data—
Mon 12 Oct— 22:33+1 min—
Fri 9 Oct— 22:32+5 min+8 min
Thu 8 Oct— 22:290 min+1 min
Wed 7 Oct— 22:28+1 min—
Tue 6 Oct— 22:270 min—
Sat 26 SeptAmsterdam Sloterdijk 22:34No data—
Wed 9 SeptAmsterdam Sloterdijk 22:34No data—
Sun 6 SeptAmsterdam Sloterdijk 22:34No data—