Train NS 8469 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 18:26 → Hoofddorp 18:47 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 18:26 from Amsterdam Centraal · Sun 8 Nov

Next departure 18:26 today · Amsterdam Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 5 full · 7 partial · 14 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 8 full · 8 partial · 41 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 2 Nov Max en route +9 min · last fix heading to Amsterdam Centraal +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=1
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 16 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
18:26on time +1 min
18:31≈ on time ≈ +1 min
18:35≈ on time ≈ +1 min
18:41 / 18:43≈ on time ≈ +1 min
18:47on 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
Sat 7 NovSchiphol Airport 18:57Partial coverage0 min+1 min
Fri 6 NovSchiphol Airport 18:57Partial coverage0 min+1 min
Thu 5 Nov— 18:49No data—
Wed 4 Nov— 18:490 min—
Mon 2 NovAmsterdam Centraal 18:59Partial coverage+8 min+9 min
Sun 1 NovSchiphol Airport 18:57Partial coverage0 min—
Sat 31 OctSchiphol Airport 18:57Partial coverage0 min—
Fri 30 OctSchiphol Airport 18:57No data—
Thu 29 Oct— 18:490 min—
Wed 28 Oct— 19:00+1 min—
Tue 27 Oct— 18:53No data—
Mon 26 Oct— 18:49No data—
Sun 25 OctSchiphol Airport 18:57No data—
Sat 24 OctSchiphol Airport 18:58No data—
Fri 23 OctSchiphol Airport 18:53Partial coverage0 min—
Thu 22 OctAmsterdam Centraal 19:05No data—
Wed 21 OctAmsterdam Lelylaan 18:49No data—
Tue 20 OctSchiphol Airport 18:50No data—
Mon 19 OctSchiphol Airport 18:57No data—
Fri 16 OctSchiphol Airport 18:57No data—
Thu 15 OctAmsterdam Centraal 18:52No data—
Wed 14 OctSchiphol Airport 18:57No data—
Tue 13 OctAmsterdam Lelylaan 18:49No data—
Mon 12 OctSchiphol Airport 18:57Partial coverage0 min—
Sun 11 OctSchiphol Airport 18:570 min—
Sat 10 OctSchiphol Airport 18:59+2 min+3 min
Fri 9 OctAmsterdam Lelylaan 18:49Partial coverage+2 min+2 min
Thu 8 Oct— 18:51+1 min+2 min
Wed 7 Oct— 18:490 min—
Tue 6 Oct— 18:49+1 min—