Train NS 8264 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

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

Next departure 19:17 today · Hoofddorp
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 6 full · 3 partial · 18 no data
On-time · 90 days
100%
11/11 runs under 3 min
RT coverage: 8 full · 3 partial · 28 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 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

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

  • Early 0% · 0
  • On time 100% · 11
  • 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=1
  • 100% W n=2
  • 100% T n=2
  • 100% F n=2
  • — S n=0
  • 100% S n=3

Stops and timetable

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

Last 90 days, 11 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
19:17on time on time
19:21 / 19:22≈ on time ≈ on time
19:29≈ on time ≈ on time
19:33≈ on time ≈ on time
19:39on 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
Wed 4 Nov— 19:39No data—
Tue 3 Nov— 19:39No data—
Sun 1 NovAmsterdam Sloterdijk 19:48Partial coverage+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 19:47No data—
Fri 30 Oct— 19:40No data—
Thu 29 Oct— 19:410 min—
Wed 28 Oct— 19:51No data—
Tue 27 Oct— 19:41No data—
Mon 26 Oct— 19:42No data—
Sun 25 OctAmsterdam Sloterdijk 19:47No data—
Sat 24 OctAmsterdam Sloterdijk 19:48No data—
Fri 23 OctSchiphol Airport 19:40Partial coverage0 min—
Thu 22 Oct— 19:41No data—
Wed 21 Oct— 19:40No data—
Mon 19 Oct— 19:40No data—
Sun 18 OctAmsterdam Sloterdijk 19:47Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 19:48No data—
Fri 16 OctAmsterdam Sloterdijk 19:47No data—
Thu 15 Oct— 19:43No data—
Wed 14 OctAmsterdam Sloterdijk 19:42No data—
Tue 13 Oct— 19:39No data—
Mon 12 Oct— 19:410 min—
Sun 11 OctAmsterdam Sloterdijk 19:480 min+2 min
Sat 10 Oct— 19:41No data—
Fri 9 Oct— 19:44+1 min+2 min
Thu 8 Oct— 19:400 min—
Wed 7 Oct— 19:400 min—
Tue 6 Oct— 19:400 min—
Sat 26 SeptAmsterdam Sloterdijk 19:47No data—
Sun 20 SeptAmsterdam Sloterdijk 19:50No data—