Train NS 8354 Hoofddorp – Amsterdam Centraal

Hoofddorp 16:23 → Amsterdam Centraal 16:46 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 16:55 0 min

  1. Hoofddorp16:23
  2. Schiphol Airport16:27
  3. Amsterdam Lelylaan16:35
  4. Amsterdam Sloterdijk16:39
  5. Amsterdam Centraal16:46

Next service: tomorrow 16:23 from Hoofddorp · Mon 9 Nov

Next departure 16:23 tomorrow · Hoofddorp
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 3 full · 12 partial · 13 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 4 full · 15 partial · 59 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

  • Sat 10 Oct Max en route +16 min · last fix heading to Amsterdam Lelylaan +16 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 17
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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:23on time +1 min
16:27 / 16:29— —
16:35— —
16:39 / 16:40— —
16:46— —

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
Sun 8 NovAmsterdam Sloterdijk 16:55Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 16:54Partial coverage+1 min—
Fri 6 NovAmsterdam Sloterdijk 16:54No data—
Thu 5 NovAmsterdam Sloterdijk 16:54No data—
Wed 4 NovAmsterdam Sloterdijk 16:54Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 16:54No data—
Mon 2 NovAmsterdam Sloterdijk 16:54Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 16:54+4 min+4 min
Sat 31 OctAmsterdam Sloterdijk 16:57Partial coverage+2 min+5 min
Fri 30 OctAmsterdam Sloterdijk 16:55No data—
Thu 29 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 16:54No data—
Mon 26 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Sun 25 OctAmsterdam Sloterdijk 16:54No data—
Sat 24 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 16:54No data—
Wed 21 OctAmsterdam Sloterdijk 16:56No data—
Tue 20 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 16:54No data—
Fri 16 OctAmsterdam Sloterdijk 16:54No data—
Thu 15 OctAmsterdam Sloterdijk 16:54No data—
Wed 14 OctAmsterdam Sloterdijk 16:54No data—
Tue 13 OctAmsterdam Sloterdijk 17:01No data—
Mon 12 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 16:540 min—
Sat 10 OctAmsterdam Lelylaan 17:21+16 min+16 min
Fri 9 OctAmsterdam Sloterdijk 16:54Partial coverage+1 min+1 min
Thu 8 OctAmsterdam Sloterdijk 16:54Partial coverage0 min—