Train NS 8124 Hoofddorp → Amsterdam Centraal

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

NS 8124 Hoofddorp–Amsterdam Centraal: final delay under 3 min on 17 of its 17 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 10:58 (GMT+1).

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: tomorrow 09:02 from Hoofddorp · Mon 23 Nov

Next departure 09:02 tomorrow · Hoofddorp
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 9 no data
On-time · 90 days
100%
27/27 runs under 3 min
RT coverage: 0 full · 27 partial · 49 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: 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 27
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=4
  • 100% W n=6
  • 100% T n=4
  • 100% F n=4
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 27 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
09:02on time on time
09:07 / 09:09— —
09:15— —
09:19— —
09: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
Fri 20 NovAmsterdam Sloterdijk 09:33Partial coverage0 min—
Thu 19 NovAmsterdam Sloterdijk 09:34Partial coverage+1 min+1 min
Wed 18 NovAmsterdam Sloterdijk 09:34Partial coverage0 min—
Tue 17 NovAmsterdam Sloterdijk 09:33Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 09:34Partial coverage0 min+1 min
Fri 13 NovAmsterdam Sloterdijk 09:33Partial coverage0 min—
Thu 12 NovAmsterdam Sloterdijk 09:34Partial coverage+1 min—
Wed 11 NovAmsterdam Sloterdijk 09:34Partial coverage0 min—
Tue 10 NovAmsterdam Sloterdijk 09:34Partial coverage0 min—
Mon 9 NovAmsterdam Sloterdijk 09:34Partial coverage0 min+1 min
Sun 8 NovAmsterdam Sloterdijk 09:34Partial coverage0 min+1 min
Sat 7 NovAmsterdam Sloterdijk 09:34Partial coverage0 min+1 min
Fri 6 NovAmsterdam Sloterdijk 09:33No data—
Thu 5 NovAmsterdam Sloterdijk 09:34No data—
Wed 4 NovAmsterdam Sloterdijk 09:34Partial coverage0 min+1 min
Tue 3 NovAmsterdam Sloterdijk 09:34No data—
Mon 2 NovAmsterdam Sloterdijk 09:34No data—
Sun 1 NovAmsterdam Sloterdijk 09:33Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 09:33Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 09:33No data—
Thu 29 OctAmsterdam Sloterdijk 09:33No data—
Wed 28 OctAmsterdam Sloterdijk 09:33Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 09:34No data—
Mon 26 OctAmsterdam Sloterdijk 09:33No data—
Sun 25 OctAmsterdam Sloterdijk 09:33No data—
Sat 24 OctAmsterdam Sloterdijk 09:34Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 09:33No data—
Thu 22 OctAmsterdam Sloterdijk 09:33Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 09:37Partial coverage0 min—
Tue 20 OctAmsterdam Sloterdijk 09:34Partial coverage0 min—