Train NS 8456 Hoofddorp – Amsterdam Centraal

Hoofddorp 17:13 → Amsterdam Centraal 17:35 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 17:43 No data

  1. Hoofddorp17:13
  2. Schiphol Airport17:17
  3. Amsterdam Lelylaan17:24
  4. Amsterdam Sloterdijk17:28
  5. Amsterdam Centraal17:35

Next service: tomorrow 17:13 from Hoofddorp · Sun 8 Nov

Next departure 17:13 tomorrow · Hoofddorp
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 7 full · 6 partial · 14 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 9 full · 6 partial · 61 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

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
  • — W n=0
  • 100% T n=2
  • 100% F n=5
  • 100% S n=1
  • 100% S n=2

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
17:13on time on time
17:17 / 17:18≈ on time ≈ on time
17:24≈ on time ≈ on time
17:28 / 17:29≈ on time ≈ on time
17:35on 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 17:43No data—
Fri 6 NovAmsterdam Sloterdijk 17:43Partial coverage0 min—
Thu 5 NovAmsterdam Sloterdijk 17:42No data—
Wed 4 NovAmsterdam Sloterdijk 17:42No data—
Mon 2 NovAmsterdam Sloterdijk 17:390 min—
Sun 1 NovAmsterdam Sloterdijk 17:43Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 17:43Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 17:43Partial coverage0 min—
Thu 29 OctAmsterdam Sloterdijk 17:39No data—
Wed 28 OctAmsterdam Sloterdijk 17:42No data—
Tue 27 OctAmsterdam Sloterdijk 17:42No data—
Mon 26 OctAmsterdam Sloterdijk 17:420 min—
Sun 25 OctAmsterdam Sloterdijk 17:43No data—
Sat 24 OctAmsterdam Sloterdijk 17:51Partial coverageNo data—
Fri 23 OctAmsterdam Sloterdijk 17:430 min—
Thu 22 OctAmsterdam Sloterdijk 17:420 min—
Wed 21 OctAmsterdam Sloterdijk 17:42No data—
Tue 20 OctAmsterdam Sloterdijk 17:420 min—
Mon 19 OctAmsterdam Sloterdijk 17:42No data—
Fri 16 OctAmsterdam Sloterdijk 17:44Partial coverage0 min—
Thu 15 OctAmsterdam Sloterdijk 17:42No data—
Wed 14 OctAmsterdam Sloterdijk 17:43No data—
Tue 13 OctAmsterdam Sloterdijk 17:42No data—
Mon 12 OctAmsterdam Sloterdijk 17:420 min—
Sun 11 OctAmsterdam Sloterdijk 17:430 min—
Sat 10 OctAmsterdam Sloterdijk 17:49No data—
Fri 9 OctAmsterdam Sloterdijk 17:43Partial coverage0 min+1 min
Thu 8 OctAmsterdam Sloterdijk 17:43+1 min—
Wed 7 OctAmsterdam Sloterdijk 17:42No data—
Tue 6 OctAmsterdam Sloterdijk 17:420 min—