Train NS 8320 Hoofddorp – Amsterdam Centraal

Hoofddorp 07:53 → Amsterdam Centraal 08:17 Mon, Tue, Wed, Thu, Fri 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 08:28 No data

  1. Hoofddorp07:53
  2. Schiphol Airport07:57
  3. Amsterdam Lelylaan08:05
  4. Amsterdam Sloterdijk08:09
  5. Amsterdam Centraal08:17

Next service: Monday 07:53 from Hoofddorp · Mon 9 Nov

Next departure 07:53 Monday · Hoofddorp
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 5 full · 8 partial · 9 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 5 full · 10 partial · 50 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: 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 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, 15 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
07:53on time on time
07:57 / 07:59≈ on time ≈ on time
08:05≈ on time ≈ on time
08:09 / 08:10≈ on time ≈ on time
08:17on 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 08:28No data—
Thu 5 NovAmsterdam Sloterdijk 08:24No data—
Wed 4 NovAmsterdam Sloterdijk 08:24Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 08:24No data—
Mon 2 NovAmsterdam Sloterdijk 08:24Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 08:240 min—
Thu 29 OctAmsterdam Sloterdijk 08:24No data—
Wed 28 OctAmsterdam Sloterdijk 08:25Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 08:25No data—
Mon 26 OctAmsterdam Sloterdijk 08:25Partial coverage+2 min+2 min
Fri 23 OctAmsterdam Sloterdijk 08:260 min—
Thu 22 OctAmsterdam Sloterdijk 08:24Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 08:25No data—
Tue 20 OctAmsterdam Sloterdijk 08:240 min—
Mon 19 OctAmsterdam Sloterdijk 08:26Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 08:290 min—
Thu 15 OctAmsterdam Sloterdijk 08:24No data—
Wed 14 OctAmsterdam Sloterdijk 08:25Partial coverage0 min—
Tue 13 OctAmsterdam Sloterdijk 08:25No data—
Mon 12 OctAmsterdam Sloterdijk 08:25No data—
Fri 9 OctAmsterdam Sloterdijk 08:25+1 min—
Thu 8 OctAmsterdam Sloterdijk 08:25Partial coverage0 min—
Wed 7 OctAmsterdam Sloterdijk 08:27Partial coverage+1 min+3 min
Tue 6 OctAmsterdam Sloterdijk 08:24Partial coverage0 min—
Fri 2 OctAmsterdam Sloterdijk 08:24No data—
Thu 1 OctAmsterdam Sloterdijk 08:25No data—
Wed 30 SeptAmsterdam Sloterdijk 08:25No data—
Tue 29 SeptAmsterdam Sloterdijk 08:24No data—
Mon 28 SeptAmsterdam Sloterdijk 08:25No data—
Fri 25 SeptAmsterdam Sloterdijk 08:25No data—