Train NS 8462 Hoofddorp – Amsterdam Centraal

Hoofddorp 18:43 → Amsterdam Centraal 19:05 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 19:13 0 min

  1. Hoofddorp18:43
  2. Schiphol Airport18:47
  3. Amsterdam Lelylaan18:54
  4. Amsterdam Sloterdijk18:58
  5. Amsterdam Centraal19:05

Next service: tomorrow 18:43 from Hoofddorp · Sun 8 Nov

Next departure 18:43 tomorrow · Hoofddorp
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 10 full · 5 partial · 12 no data
On-time · 90 days
89%
16/18 runs under 3 min
RT coverage: 13 full · 5 partial · 38 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: +3 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

  • Fri 23 Oct Max en route +5 min · last fix heading to Amsterdam Sloterdijk +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 16
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 33% 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, 18 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:43on time on time
18:47 / 18:48≈ on time ≈ on time
18:54≈ on time ≈ on time
18:58 / 18:59≈ on time ≈ on time
19:05on 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
Sat 7 NovAmsterdam Sloterdijk 19:13Partial coverage0 min—
Fri 6 NovHoofddorp 19:04Partial coverage0 min—
Thu 5 Nov— 19:04No data—
Wed 4 Nov— 19:04No data—
Mon 2 Nov— 19:040 min—
Sun 1 NovAmsterdam Sloterdijk 19:13Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 19:13Partial coverage+1 min+1 min
Fri 30 OctAmsterdam Lelylaan 19:08No data—
Thu 29 Oct— 19:060 min—
Wed 28 Oct— 19:060 min—
Tue 27 Oct— 18:54No data—
Mon 26 Oct— 19:060 min—
Sun 25 OctAmsterdam Sloterdijk 19:13No data—
Sat 24 OctHoofddorp 19:39No data—
Fri 23 OctAmsterdam Sloterdijk 19:13Partial coverage+5 min+5 min
Thu 22 OctHoofddorp 19:06No data—
Wed 21 Oct— 19:06No data—
Tue 20 OctHoofddorp 19:050 min—
Mon 19 OctHoofddorp 19:06No data—
Fri 16 OctAmsterdam Sloterdijk 20:04No data—
Thu 15 Oct— 19:10No data—
Wed 14 OctAmsterdam Sloterdijk 19:090 min—
Tue 13 Oct— 19:06No data—
Mon 12 OctHoofddorp 19:060 min—
Sun 11 OctAmsterdam Sloterdijk 19:130 min—
Sat 10 OctAmsterdam Sloterdijk 19:130 min+1 min
Fri 9 Oct— 19:10+4 min+4 min
Thu 8 Oct— 19:060 min—
Wed 7 Oct— 19:060 min—
Tue 6 Oct— 19:050 min—