Train NS 8366 Hoofddorp – Amsterdam Centraal

Hoofddorp 19:23 → Amsterdam Centraal 19:46 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 17 November +1 min

Next service: today 19:23 from Hoofddorp · Wed 18 Nov

Next departure 19:23 today · Hoofddorp
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 10 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 18 full · 4 partial · 23 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Sun 1 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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:23on time on time
19:27 / 19:29≈ on time ≈ on time
19:35≈ on time ≈ +1 min
19:39 / 19:40≈ on time ≈ +1 min
19:46on 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
Tue 17 Nov— 19:47+1 min+1 min
Mon 16 Nov— 19:47No data—
Sun 15 NovAmsterdam Sloterdijk 19:540 min+2 min
Sat 14 NovAmsterdam Sloterdijk 19:540 min—
Fri 13 Nov— 19:49+2 min+2 min
Thu 12 Nov— 19:490 min—
Wed 11 Nov— 19:48+1 min—
Tue 10 Nov— 19:49+1 min+1 min
Mon 9 Nov— 19:480 min—
Sat 7 NovAmsterdam Sloterdijk 19:54Partial coverage0 min—
Fri 6 Nov— 19:48+1 min—
Thu 5 Nov— 19:48No data—
Wed 4 Nov— 19:48+1 min—
Tue 3 Nov— 19:48No data—
Mon 2 Nov— 19:480 min—
Sun 1 NovAmsterdam Sloterdijk 19:54Partial coverage+3 min+3 min
Sat 31 OctAmsterdam Sloterdijk 19:54Partial coverage+1 min+1 min
Wed 28 Oct— 19:47No data—
Tue 27 Oct— 19:48No data—
Mon 26 OctAmsterdam Sloterdijk 19:53No data—
Sun 25 OctAmsterdam Sloterdijk 19:55No data—
Sat 24 OctAmsterdam Sloterdijk 19:56No data—
Fri 23 OctHoofddorp 19:47Partial coverage0 min—
Thu 22 Oct— 19:48No data—
Wed 21 Oct— 19:48No data—
Mon 19 Oct— 19:47No data—
Fri 16 OctAmsterdam Sloterdijk 19:53No data—
Thu 15 Oct— 19:48No data—
Wed 14 OctAmsterdam Sloterdijk 19:54No data—
Tue 13 Oct— 19:48No data—