Train NS 8432 Hoofddorp – Amsterdam Centraal

Hoofddorp 11:13 → Amsterdam Centraal 11:34 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

Running now · updated 11:16

Heading to Amsterdam Centraal No data

Estimated arrival at Amsterdam Centraal 11:34 · 37 km/h

  1. Hoofddorp11:13
  2. Schiphol Airport11:17
  3. Amsterdam Lelylaan11:24
  4. Amsterdam Sloterdijk11:28
  5. Amsterdam Centraal11:34
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 10 full · 7 partial · 11 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 10 full · 8 partial · 60 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

  • Sat 10 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=4
  • 67% 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, 18 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 10Today
11:13on time on time
11:17 / 11:18≈ on time ≈ on time
11:24≈ on time ≈ on time
11:28≈ on time ≈ on time
11:34on 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 NovHoofddorp 11:14No data—
Wed 4 NovAmsterdam Sloterdijk 11:430 min—
Tue 3 NovAmsterdam Sloterdijk 11:43No data—
Mon 2 NovAmsterdam Sloterdijk 11:44Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 11:450 min—
Sat 31 OctAmsterdam Sloterdijk 11:430 min—
Fri 30 OctAmsterdam Sloterdijk 11:440 min—
Thu 29 OctAmsterdam Sloterdijk 11:43No data—
Wed 28 OctAmsterdam Sloterdijk 11:43No data—
Tue 27 OctAmsterdam Sloterdijk 11:43No data—
Mon 26 OctAmsterdam Sloterdijk 11:43Partial coverage0 min—
Sun 25 OctAmsterdam Sloterdijk 11:43No data—
Sat 24 OctAmsterdam Sloterdijk 11:430 min—
Fri 23 OctAmsterdam Sloterdijk 11:470 min—
Thu 22 OctAmsterdam Sloterdijk 11:42Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 11:42No data—
Tue 20 OctAmsterdam Sloterdijk 11:43Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 11:54No data—
Fri 16 OctAmsterdam Sloterdijk 11:500 min—
Thu 15 OctAmsterdam Sloterdijk 11:42No data—
Wed 14 OctAmsterdam Sloterdijk 11:42No data—
Tue 13 OctAmsterdam Sloterdijk 11:47No data—
Mon 12 OctAmsterdam Sloterdijk 11:44Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 11:430 min—
Sat 10 OctAmsterdam Sloterdijk 11:43+3 min+3 min
Fri 9 OctAmsterdam Sloterdijk 11:430 min—
Thu 8 OctAmsterdam Sloterdijk 11:44Partial coverage+1 min+2 min
Wed 7 OctHoofddorp 12:01Partial coverage0 min—
Tue 6 OctAmsterdam Sloterdijk 11:43Partial coverage0 min—
Fri 2 OctAmsterdam Sloterdijk 11:43No data—