Train NS 8322 Hoofddorp – Amsterdam Centraal

Hoofddorp 08:23 → Amsterdam Centraal 08:46 Mon, Tue, Wed, Thu, Fri 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 08:54 0 min

  1. Hoofddorp08:23
  2. Schiphol Airport08:27
  3. Amsterdam Lelylaan08:35
  4. Amsterdam Sloterdijk08:39
  5. Amsterdam Centraal08:46

Next service: Monday 08:23 from Hoofddorp · Mon 23 Nov

Next departure 08:23 Monday · Hoofddorp
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 5 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 0 full · 23 partial · 40 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=5
  • 100% T n=3
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
08:23on time on time
08:27 / 08:29— —
08:35— —
08:39 / 08:40— —
08:46— —

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 20 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Thu 19 NovAmsterdam Sloterdijk 09:07Partial coverageNo data—
Wed 18 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Tue 17 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 08:54Partial coverage+1 min+3 min
Fri 13 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Thu 12 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Wed 11 NovAmsterdam Sloterdijk 08:54Partial coverage+1 min—
Tue 10 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Mon 9 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Fri 6 NovAmsterdam Sloterdijk 08:54No data—
Thu 5 NovAmsterdam Sloterdijk 08:54No data—
Wed 4 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Mon 2 NovAmsterdam Sloterdijk 08:54Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 08:54No data—
Thu 29 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 09:00Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 08:54No data—
Wed 21 OctAmsterdam Sloterdijk 08:54No data—
Tue 20 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 08:54Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 08:54No data—
Thu 15 OctAmsterdam Sloterdijk 08:54No data—
Wed 14 OctAmsterdam Sloterdijk 08:54No data—
Tue 13 OctAmsterdam Sloterdijk 08:54No data—
Mon 12 OctAmsterdam Sloterdijk 08:58No data—