Train NS 8352 Hoofddorp – Amsterdam Centraal

Hoofddorp 15:53 → Amsterdam Centraal 16:17 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 15:53 from Hoofddorp · Fri 20 Nov

Next departure 15:53 today · Hoofddorp
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 4 full · 15 partial · 10 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 6 full · 20 partial · 53 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

Worst days

  • Mon 9 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 26 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
15:53on time on time
15:57 / 15:59≈ on time ≈ +2 min
16:05≈ on time ≈ +2 min
16:09 / 16:10≈ on time ≈ +2 min
16:17on 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
Thu 19 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Wed 18 Nov— 16:09No data—
Tue 17 NovAmsterdam Sloterdijk 16:24Partial coverage0 min+3 min
Mon 16 NovAmsterdam Sloterdijk 16:25Partial coverage0 min—
Sun 15 NovAmsterdam Sloterdijk 16:240 min—
Sat 14 NovAmsterdam Sloterdijk 16:240 min—
Fri 13 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Thu 12 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Wed 11 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Tue 10 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Mon 9 NovAmsterdam Sloterdijk 16:24Partial coverage+3 min+3 min
Sun 8 NovAmsterdam Sloterdijk 16:25Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Fri 6 NovAmsterdam Sloterdijk 16:24No data—
Thu 5 Nov— 16:19No data—
Wed 4 NovAmsterdam Sloterdijk 16:24Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 16:24No data—
Mon 2 NovAmsterdam Sloterdijk 16:29Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 16:26+2 min+2 min
Sat 31 OctAmsterdam Sloterdijk 16:24Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 16:24No data—
Thu 29 OctAmsterdam Sloterdijk 16:24No data—
Wed 28 OctAmsterdam Sloterdijk 16:250 min—
Tue 27 OctAmsterdam Sloterdijk 16:25No data—
Mon 26 OctAmsterdam Sloterdijk 16:31No data—
Sun 25 OctAmsterdam Sloterdijk 16:24No data—
Sat 24 OctAmsterdam Sloterdijk 16:26Partial coverage+1 min+3 min
Fri 23 OctAmsterdam Sloterdijk 16:24No data—
Thu 22 OctAmsterdam Sloterdijk 16:25Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 16:25No data—