Train NS 8459 Amsterdam Centraal → Hoofddorp

Amsterdam Centraal 15:56 → Hoofddorp 16:17 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

NS 8459 Amsterdam Centraal–Hoofddorp: final delay under 3 min on 18 of its 20 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 14:26 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +1 min

Next service: today 15:56 from Amsterdam Centraal · Sun 22 Nov

Next departure 15:56 today · Amsterdam Centraal
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 12 full · 8 partial · 9 no data
On-time · 90 days
90%
27/30 runs under 3 min
RT coverage: 19 full · 11 partial · 49 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 Hoofddorp, 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 +15 min · last fix heading to Amsterdam Lelylaan +15 min
  • Sat 31 Oct Max en route +8 min · last fix heading to Schiphol Airport +8 min
  • Fri 13 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 27
  • 3–10 min 7% · 2
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 60% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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:56on time on time
16:01≈ on time ≈ on time
16:05≈ on time ≈ +1 min
16:11 / 16:13≈ on time ≈ +1 min
16:17on 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
Sat 21 NovSchiphol Airport 16:27Partial coverage+1 min—
Fri 20 NovSchiphol Airport 16:27Partial coverage0 min—
Thu 19 NovSchiphol Airport 16:270 min—
Wed 18 Nov— 16:18No data—
Tue 17 NovSchiphol Airport 16:28+1 min—
Mon 16 NovSchiphol Airport 16:280 min—
Sun 15 NovSchiphol Airport 16:27+3 min+3 min
Sat 14 Nov— 16:18No data—
Fri 13 NovSchiphol Airport 16:29Partial coverage+4 min+4 min
Thu 12 NovSchiphol Airport 16:270 min+1 min
Wed 11 NovSchiphol Airport 16:270 min—
Tue 10 NovSchiphol Airport 16:270 min—
Mon 9 NovSchiphol Airport 16:270 min—
Sun 8 NovSchiphol Airport 16:28Partial coverage0 min—
Sat 7 NovSchiphol Airport 16:27Partial coverage0 min—
Fri 6 NovSchiphol Airport 16:27No data—
Thu 5 NovSchiphol Airport 16:27No data—
Wed 4 NovSchiphol Airport 16:27+1 min+1 min
Tue 3 NovSchiphol Airport 16:27No data—
Mon 2 NovSchiphol Airport 16:39No data—
Sun 1 NovSchiphol Airport 16:28Partial coverage0 min+1 min
Sat 31 OctSchiphol Airport 16:35Partial coverage+8 min+8 min
Fri 30 OctSchiphol Airport 16:27No data—
Thu 29 OctSchiphol Airport 16:270 min—
Wed 28 OctSchiphol Airport 16:270 min—
Tue 27 OctSchiphol Airport 16:29No data—
Mon 26 OctSchiphol Airport 16:270 min—
Sun 25 OctSchiphol Airport 16:28No data—
Sat 24 OctSchiphol Airport 16:27Partial coverage0 min—
Fri 23 OctSchiphol Airport 16:27Partial coverage0 min—