Train NS 8359 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 16:13 → Hoofddorp 16:34 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 16:44 No data

  1. Amsterdam Centraal16:13
  2. Amsterdam Sloterdijk16:19
  3. Amsterdam Lelylaan16:23
  4. Schiphol Airport16:29
  5. Hoofddorp16:34

Next service: tomorrow 16:13 from Amsterdam Centraal · Fri 6 Nov

Next departure 16:13 tomorrow · Amsterdam Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 5 full · 8 partial · 15 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 5 full · 9 partial · 64 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: +2 min

Last 30 days

Arrival delay at Hoofddorp, 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 +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=4
  • 100% T n=2
  • 100% F n=1
  • 50% S n=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 14 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:13on time on time
16:19≈ +1 min ≈ +1 min
16:23≈ +1 min ≈ +2 min
16:29 / 16:30≈ +1 min ≈ +3 min
16:34+2 min +4 min

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
Thu 5 NovSchiphol Airport 16:44No data—
Wed 4 NovSchiphol Airport 16:44Partial coverage0 min—
Tue 3 NovSchiphol Airport 16:44No data—
Mon 2 NovSchiphol Airport 16:52No data—
Sun 1 NovSchiphol Airport 16:46+2 min+2 min
Sat 31 OctSchiphol Airport 16:44No data—
Fri 30 OctSchiphol Airport 16:44No data—
Thu 29 OctSchiphol Airport 16:45Partial coverage0 min—
Wed 28 OctSchiphol Airport 16:45Partial coverage0 min—
Tue 27 OctSchiphol Airport 16:44No data—
Mon 26 OctSchiphol Airport 16:47No data—
Sun 25 OctSchiphol Airport 16:46No data—
Sat 24 OctSchiphol Airport 16:440 min—
Fri 23 OctSchiphol Airport 16:46No data—
Thu 22 OctSchiphol Airport 16:45No data—
Wed 21 OctSchiphol Airport 16:47No data—
Tue 20 OctSchiphol Airport 16:44Partial coverage0 min—
Mon 19 OctSchiphol Airport 16:47No data—
Fri 16 OctSchiphol Airport 16:44No data—
Thu 15 OctSchiphol Airport 16:44No data—
Wed 14 OctSchiphol Airport 16:44Partial coverage0 min—
Tue 13 OctSchiphol Airport 16:45No data—
Mon 12 OctSchiphol Airport 16:44Partial coverage0 min—
Sun 11 OctSchiphol Airport 16:440 min—
Sat 10 OctSchiphol Airport 16:46+5 min+5 min
Fri 9 OctSchiphol Airport 16:46+2 min+2 min
Thu 8 OctSchiphol Airport 16:45Partial coverage0 min—
Wed 7 OctSchiphol Airport 16:46Partial coverage+1 min+1 min
Tue 6 OctSchiphol Airport 16:44Partial coverage0 min—
Fri 2 OctSchiphol Airport 16:47No data—