Train NS 8254 Hoofddorp – Amsterdam Centraal

Hoofddorp 16:47 → Amsterdam Centraal 17:09 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 17:18 0 min

  1. Hoofddorp16:47
  2. Schiphol Airport16:51
  3. Amsterdam Lelylaan16:59
  4. Amsterdam Sloterdijk17:03
  5. Amsterdam Centraal17:09

Next service: tomorrow 16:47 from Hoofddorp · Sat 7 Nov

Next departure 16:47 tomorrow · Hoofddorp
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 2 full · 11 partial · 17 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 12 full · 13 partial · 47 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • 100% S n=3

Stops and timetable

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

Last 90 days, 25 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
16:47on time on time
16:51 / 16:53≈ on time ≈ on time
16:59≈ on time ≈ on time
17:03≈ on time ≈ on time
17:09on 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 17:18Partial coverage0 min—
Thu 5 NovAmsterdam Sloterdijk 17:17No data—
Wed 4 NovAmsterdam Sloterdijk 17:17No data—
Tue 3 NovAmsterdam Sloterdijk 17:17No data—
Mon 2 NovAmsterdam Sloterdijk 17:19No data—
Sun 1 NovAmsterdam Sloterdijk 17:180 min—
Sat 31 OctAmsterdam Sloterdijk 17:18Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 17:18No data—
Thu 29 OctAmsterdam Sloterdijk 17:17Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 17:17Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 17:17No data—
Mon 26 OctAmsterdam Sloterdijk 17:17No data—
Sun 25 OctAmsterdam Sloterdijk 17:21No data—
Sat 24 OctAmsterdam Sloterdijk 17:17Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 17:24No data—
Thu 22 OctAmsterdam Sloterdijk 17:17Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 17:17No data—
Tue 20 OctAmsterdam Sloterdijk 17:19Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 17:19No data—
Sun 18 OctAmsterdam Sloterdijk 17:18Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 17:22No data—
Fri 16 OctAmsterdam Sloterdijk 17:18No data—
Thu 15 OctAmsterdam Sloterdijk 17:17No data—
Wed 14 OctAmsterdam Sloterdijk 17:18No data—
Tue 13 OctAmsterdam Sloterdijk 17:18No data—
Mon 12 OctAmsterdam Sloterdijk 17:34Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 17:18+1 min—
Sat 10 OctAmsterdam Sloterdijk 17:17No data—
Fri 9 OctAmsterdam Sloterdijk 17:18Partial coverage0 min—
Thu 8 OctAmsterdam Sloterdijk 17:17Partial coverage0 min—