Train NS 8468 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November +3 min

Next service: today 20:13 from Hoofddorp · Thu 5 Nov

Next departure 20:13 today · Hoofddorp
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 15 full · 0 partial · 9 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 16 full · 0 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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 4 Nov Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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
20:13on time on time
20:17 / 20:18≈ on time ≈ on time
20:24≈ on time ≈ +1 min
20:28≈ on time ≈ +1 min
20:34on time +2 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
Wed 4 Nov— 20:39+3 min+4 min
Sun 1 NovAmsterdam Sloterdijk 20:430 min—
Sat 31 OctAmsterdam Sloterdijk 20:430 min—
Fri 30 Oct— 20:370 min—
Thu 29 Oct— 20:38+2 min+2 min
Tue 27 Oct— 20:36No data—
Mon 26 Oct— 20:35No data—
Sun 25 OctAmsterdam Sloterdijk 20:43No data—
Sat 24 OctAmsterdam Sloterdijk 20:44No data—
Fri 23 Oct— 20:360 min—
Thu 22 Oct— 20:360 min—
Wed 21 Oct— 20:36No data—
Tue 20 Oct— 20:360 min—
Mon 19 Oct— 20:35No data—
Fri 16 Oct— 20:370 min—
Thu 15 Oct— 20:35No data—
Wed 14 Oct— 20:35No data—
Tue 13 Oct— 20:36No data—
Mon 12 Oct— 20:350 min—
Sun 11 OctAmsterdam Sloterdijk 20:44+1 min+1 min
Sat 10 OctAmsterdam Sloterdijk 20:45+2 min+3 min
Fri 9 Oct— 20:360 min—
Thu 8 Oct— 20:400 min—
Wed 7 Oct— 20:360 min—
Tue 6 Oct— 20:36+1 min—
Sat 26 SeptAmsterdam Sloterdijk 20:43No data—
Sun 20 SeptAmsterdam Sloterdijk 20:43No data—
Sat 19 SeptAmsterdam Sloterdijk 20:45No data—
Sun 6 SeptAmsterdam Sloterdijk 20:44No data—
Sat 5 SeptAmsterdam Sloterdijk 20:44No data—