Train NS 8350 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November +1 min

Next service: today 15:23 from Hoofddorp · Sun 8 Nov

Next departure 15:23 today · Hoofddorp
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 8 full · 6 partial · 13 no data
On-time · 90 days
88%
15/17 runs under 3 min
RT coverage: 11 full · 6 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Tue 6 Oct Max en route +8 min · last fix heading to Amsterdam Sloterdijk +8 min
  • Sat 31 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 15
  • 3–10 min 12% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 67% T n=3
  • 100% W n=3
  • 100% T n=2
  • 100% F n=1
  • 67% 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, 17 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
15:23on time on time
15:27 / 15:29≈ on time ≈ on time
15:35≈ on time ≈ on time
15:39 / 15:40≈ on time ≈ on time
15:46on 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 15:54Partial coverage+1 min+2 min
Fri 6 NovAmsterdam Sloterdijk 15:54No data—
Thu 5 NovAmsterdam Sloterdijk 15:54No data—
Wed 4 NovAmsterdam Sloterdijk 15:540 min—
Tue 3 NovAmsterdam Sloterdijk 15:58No data—
Mon 2 NovAmsterdam Sloterdijk 16:090 min—
Sun 1 NovAmsterdam Sloterdijk 15:55Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 15:54Partial coverage+3 min+3 min
Fri 30 OctAmsterdam Sloterdijk 15:54No data—
Thu 29 OctAmsterdam Sloterdijk 15:540 min—
Wed 28 OctAmsterdam Sloterdijk 15:540 min—
Tue 27 OctAmsterdam Sloterdijk 15:54No data—
Mon 26 OctAmsterdam Sloterdijk 15:540 min—
Sun 25 OctAmsterdam Sloterdijk 15:55No data—
Sat 24 OctAmsterdam Sloterdijk 15:54Partial coverage+1 min+1 min
Fri 23 OctAmsterdam Sloterdijk 15:54Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 15:54No data—
Wed 21 OctAmsterdam Sloterdijk 15:54No data—
Tue 20 OctAmsterdam Sloterdijk 15:540 min—
Mon 19 OctAmsterdam Sloterdijk 15:55No data—
Fri 16 OctAmsterdam Sloterdijk 15:55No data—
Thu 15 OctAmsterdam Sloterdijk 15:55No data—
Wed 14 OctAmsterdam Sloterdijk 15:54No data—
Tue 13 OctAmsterdam Sloterdijk 15:550 min—
Mon 12 OctAmsterdam Sloterdijk 15:54Partial coverage+2 min+2 min
Sun 11 OctAmsterdam Sloterdijk 15:550 min+1 min
Sat 10 OctAmsterdam Sloterdijk 15:54No data—
Fri 9 OctAmsterdam Sloterdijk 15:58Partial coverageNo data—
Thu 8 OctAmsterdam Sloterdijk 15:540 min—
Wed 7 OctAmsterdam Sloterdijk 15:540 min—