Train NS 8272 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 21:17 from Hoofddorp · Thu 5 Nov

Next departure 21:17 today · Hoofddorp
On-time · 30 days
81%
13/16 runs under 3 min
RT coverage: 14 full · 2 partial · 13 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 16 full · 2 partial · 20 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Fri 9 Oct Max en route +8 min · last fix heading to — +8 min
  • Wed 7 Oct Max en route +6 min · last fix heading to — +6 min
  • Sat 10 Oct Max en route +6 min · last fix heading to Amsterdam Sloterdijk +5 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 83% · 15
  • 3–10 min 17% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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 10
21:17on time on time
21:21 / 21:22≈ on time ≈ +1 min
21:29≈ on time ≈ +3 min
21:33≈ on time ≈ +4 min
21:39on time +5 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— 21:390 min—
Tue 3 Nov— 21:420 min—
Mon 2 Nov— 21:39+1 min+1 min
Sun 1 NovAmsterdam Sloterdijk 21:47Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 21:47No data—
Fri 30 Oct— 21:42No data—
Thu 29 Oct— 21:400 min—
Wed 28 Oct— 21:40No data—
Tue 27 Oct— 21:460 min—
Mon 26 Oct— 21:420 min—
Sun 25 OctAmsterdam Sloterdijk 21:47No data—
Sat 24 OctAmsterdam Sloterdijk 21:47No data—
Fri 23 Oct— 21:20No data—
Thu 22 Oct— 21:41No data—
Wed 21 Oct— 21:41No data—
Tue 20 Oct— 21:450 min—
Mon 19 Oct— 21:41No data—
Sun 18 OctAmsterdam Sloterdijk 21:47Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 21:47No data—
Fri 16 Oct— 21:400 min—
Thu 15 Oct— 21:42No data—
Wed 14 Oct— 21:40No data—
Tue 13 Oct— 21:41No data—
Mon 12 Oct— 21:420 min—
Sun 11 OctAmsterdam Sloterdijk 21:48+1 min—
Sat 10 OctAmsterdam Sloterdijk 21:47+5 min+6 min
Fri 9 Oct— 21:46+8 min+8 min
Thu 8 Oct— 21:410 min—
Wed 7 Oct— 21:45+6 min+6 min
Tue 6 Oct— 21:400 min—