Train NS 8264 Hoofddorp → Amsterdam Centraal

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

NS 8264 Hoofddorp–Amsterdam Centraal: final delay under 3 min on 15 of its 19 runs with data in the last 30 days (79%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 07:43 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +1 min

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

Next departure 19:17 today · Hoofddorp
On-time · 30 days
79%
15/19 runs under 3 min
RT coverage: 15 full · 4 partial · 9 no data
On-time · 90 days
85%
23/27 runs under 3 min
RT coverage: 21 full · 6 partial · 27 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: +6 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

  • Mon 16 Nov Max en route +14 min · last fix heading to — +14 min
  • Wed 18 Nov Max en route +10 min · last fix heading to — +9 min
  • Fri 13 Nov Max en route +6 min · last fix heading to — +6 min
  • Sun 15 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 23
  • 3–10 min 11% · 3
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 67% W n=3
  • 100% T n=5
  • 80% F n=5
  • 100% S n=3
  • 80% S n=5

Stops and timetable

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

Last 90 days, 27 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 +1 min
19:21 / 19:22≈ on time ≈ +2 min
19:29≈ on time ≈ +3 min
19:33≈ on time ≈ +4 min
19:39on time +6 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 NovAmsterdam Sloterdijk 19:49Partial coverage+1 min+1 min
Fri 20 NovHoofddorp 19:43Partial coverage0 min—
Thu 19 Nov— 19:390 min—
Wed 18 Nov— 19:54+9 min+10 min
Tue 17 Nov— 19:390 min—
Mon 16 Nov— 20:09+14 min+14 min
Sun 15 NovAmsterdam Sloterdijk 19:52+4 min+5 min
Sat 14 NovAmsterdam Sloterdijk 19:470 min—
Fri 13 Nov— 19:44+6 min+6 min
Thu 12 Nov— 19:390 min—
Wed 11 Nov— 19:39+1 min+1 min
Tue 10 Nov— 19:390 min+2 min
Mon 9 Nov— 19:390 min—
Sun 8 NovAmsterdam Sloterdijk 19:490 min—
Sat 7 NovAmsterdam Sloterdijk 19:48Partial coverage0 min—
Fri 6 Nov— 19:43+1 min+3 min
Thu 5 Nov— 19:430 min—
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—