Train NS 8276 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 22:17 from Hoofddorp · Sun 8 Nov

Next departure 22:17 today · Hoofddorp
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 8 full · 3 partial · 15 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 12 full · 3 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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 100% · 15
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=2
  • 100% T n=1
  • 100% F n=4
  • 100% 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, 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
22:17on time on time
22:21 / 22:22≈ on time ≈ on time
22:29≈ on time ≈ on time
22:33≈ on time ≈ on time
22:39on time on time

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