Train NS 8479 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:56 from Amsterdam Centraal · Mon 9 Nov

Next departure 20:56 today · Amsterdam Centraal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 14 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 23 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 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

  • Fri 9 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 67% F n=3
  • 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, 15 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:56on time on time
21:01≈ on time ≈ +1 min
21:05≈ on time ≈ +1 min
21:11 / 21:13≈ on time ≈ +1 min
21:17on 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
Sat 7 NovSchiphol Airport 21:27Partial coverage0 min—
Fri 6 Nov— 21:23+2 min+3 min
Thu 5 Nov— 06:19No data—
Wed 4 Nov— 21:19+1 min—
Mon 2 Nov— 21:190 min+1 min
Sun 1 NovSchiphol Airport 21:27Partial coverage0 min—
Sat 31 OctSchiphol Airport 21:27No data—
Thu 29 Oct— 21:190 min—
Wed 28 Oct— 21:18No data—
Tue 27 Oct— 21:19No data—
Mon 26 Oct— 21:18No data—
Sun 25 OctSchiphol Airport 21:27No data—
Sat 24 OctSchiphol Airport 21:27No data—
Fri 23 Oct— 21:190 min—
Thu 22 Oct— 21:19No data—
Wed 21 Oct— 21:18No data—
Tue 20 Oct— 21:210 min—
Mon 19 Oct— 21:19No data—
Fri 16 Oct— 21:18No data—
Thu 15 Oct— 21:21No data—
Wed 14 Oct— 21:23No data—
Tue 13 Oct— 21:19No data—
Mon 12 Oct— 21:190 min—
Sun 11 OctSchiphol Airport 21:270 min—
Sat 10 OctSchiphol Airport 21:270 min+1 min
Fri 9 Oct— 21:23+3 min+3 min
Thu 8 Oct— 21:190 min—
Wed 7 Oct— 21:200 min+1 min
Tue 6 Oct— 21:180 min—
Sat 26 SeptSchiphol Airport 21:27No data—