Train NS 8210 Hoofddorp – Amsterdam Centraal

Hoofddorp 05:47 → Amsterdam Centraal 06:09 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 05:47 from Hoofddorp · Sat 7 Nov

Next departure 05:47 today · Hoofddorp
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 9 full · 16 partial · 4 no data
On-time · 90 days
95%
42/44 runs under 3 min
RT coverage: 25 full · 19 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

Worst days

  • Thu 8 Oct Max en route +8 min · last fix heading to Amsterdam Sloterdijk +7 min
  • Fri 30 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 42
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=6
  • 89% T n=9
  • 88% F n=8
  • 100% S n=5
  • 100% S n=3

Stops and timetable

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

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