Train NS 8329 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 08:43 → Hoofddorp 09:04 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 08:43 from Amsterdam Centraal · Mon 9 Nov

Next departure 08:43 Monday · Amsterdam Centraal
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 1 full · 10 partial · 10 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 1 full · 13 partial · 50 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 Hoofddorp, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 6 Oct Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:43on time on time
08:48— —
08:52— —
08:58 / 09:00— —
09:04— —

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 NovSchiphol Airport 09:14No data—
Thu 5 NovSchiphol Airport 09:14No data—
Wed 4 NovSchiphol Airport 09:14Partial coverage0 min—
Tue 3 NovSchiphol Airport 09:14Partial coverage0 min—
Mon 2 NovSchiphol Airport 09:14Partial coverage0 min—
Fri 30 OctSchiphol Airport 09:15No data—
Thu 29 OctSchiphol Airport 09:16No data—
Wed 28 OctSchiphol Airport 09:14No data—
Tue 27 OctSchiphol Airport 09:15No data—
Mon 26 OctSchiphol Airport 09:18Partial coverage0 min—
Fri 23 OctSchiphol Airport 09:15No data—
Thu 22 OctSchiphol Airport 09:14Partial coverage0 min—
Wed 21 OctSchiphol Airport 09:15No data—
Tue 20 OctAmsterdam Sloterdijk 09:30Partial coverage0 min—
Mon 19 OctAmsterdam Centraal 09:32Partial coverage0 min—
Fri 16 OctSchiphol Airport 09:140 min—
Thu 15 OctSchiphol Airport 09:15No data—
Wed 14 OctSchiphol Airport 09:14Partial coverage0 min—
Tue 13 OctSchiphol Airport 09:14No data—
Mon 12 OctSchiphol Airport 09:16Partial coverage0 min—
Fri 9 OctSchiphol Airport 09:15Partial coverage0 min+1 min
Thu 8 OctSchiphol Airport 09:14Partial coverage0 min—
Wed 7 OctSchiphol Airport 09:14Partial coverage0 min—
Tue 6 OctSchiphol Airport 09:17Partial coverage+4 min+4 min
Fri 2 OctSchiphol Airport 09:15No data—
Thu 1 OctSchiphol Airport 09:15No data—
Wed 30 SeptSchiphol Airport 09:21No data—
Tue 29 SeptSchiphol Airport 09:15No data—
Mon 28 SeptSchiphol Airport 09:14No data—
Fri 25 SeptSchiphol Airport 09:15No data—