Train NS 8450 Hoofddorp → Amsterdam Centraal

Hoofddorp 15:43 → Amsterdam Centraal 16:05 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 15:43 from Hoofddorp · Sat 21 Nov

Next departure 15:43 today · Hoofddorp
On-time · 30 days
85%
17/20 runs under 3 min
RT coverage: 14 full · 6 partial · 9 no data
On-time · 90 days
90%
26/29 runs under 3 min
RT coverage: 22 full · 7 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Tue 10 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min
  • Thu 12 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min
  • Mon 9 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 26
  • 3–10 min 10% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 80% T n=5
  • 100% W n=6
  • 75% T n=4
  • 100% F n=3
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 29 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
15:43on time on time
15:47 / 15:48≈ on time ≈ +1 min
15:54≈ on time ≈ +1 min
15:58 / 15:59≈ on time ≈ +2 min
16:05on time +3 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 20 NovAmsterdam Sloterdijk 16:13Partial coverage0 min—
Thu 19 NovAmsterdam Sloterdijk 16:130 min—
Wed 18 NovAmsterdam Sloterdijk 16:120 min—
Tue 17 NovAmsterdam Sloterdijk 16:13+1 min—
Mon 16 NovAmsterdam Sloterdijk 16:140 min—
Sun 15 NovAmsterdam Sloterdijk 16:130 min—
Sat 14 NovAmsterdam Sloterdijk 16:130 min—
Fri 13 NovAmsterdam Sloterdijk 16:13Partial coverage0 min—
Thu 12 NovAmsterdam Sloterdijk 16:13+3 min+3 min
Wed 11 NovAmsterdam Sloterdijk 16:130 min—
Tue 10 NovAmsterdam Sloterdijk 16:14+3 min+3 min
Mon 9 NovAmsterdam Sloterdijk 16:13+3 min+3 min
Sun 8 NovAmsterdam Sloterdijk 16:13Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 16:13Partial coverage0 min—
Fri 6 NovAmsterdam Sloterdijk 16:14No data—
Thu 5 NovAmsterdam Sloterdijk 16:15No data—
Wed 4 NovAmsterdam Sloterdijk 16:130 min—
Tue 3 NovAmsterdam Sloterdijk 16:120 min—
Mon 2 NovAmsterdam Sloterdijk 16:19No data—
Sun 1 NovAmsterdam Sloterdijk 16:14Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 16:13Partial coverageNo data—
Fri 30 OctAmsterdam Sloterdijk 16:13No data—
Thu 29 OctAmsterdam Sloterdijk 16:130 min—
Wed 28 OctAmsterdam Sloterdijk 16:120 min—
Tue 27 OctAmsterdam Sloterdijk 16:18No data—
Mon 26 OctAmsterdam Sloterdijk 16:13No data—
Sun 25 OctAmsterdam Sloterdijk 16:13No data—
Sat 24 OctAmsterdam Sloterdijk 16:13Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 16:13No data—
Thu 22 OctAmsterdam Sloterdijk 16:13No data—