Train NS 8174 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

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

Next departure 21:32 today · Hoofddorp
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 9 full · 3 partial · 14 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 20 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

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 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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