Train NS 8164 Hoofddorp – Amsterdam Centraal

Hoofddorp 19:02 → Amsterdam Centraal 19:25 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 19:24 No data

  1. Hoofddorp19:02
  2. Schiphol Airport19:07
  3. Amsterdam Lelylaan19:15
  4. Amsterdam Sloterdijk19:19
  5. Amsterdam Centraal19:25

Next service: tomorrow 19:02 from Hoofddorp · Sun 8 Nov

Next departure 19:02 tomorrow · Hoofddorp
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 4 full · 5 partial · 17 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 7 full · 5 partial · 29 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: +1 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=1
  • 100% T n=1
  • 100% F n=3
  • 100% 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, 12 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
19:02on time on time
19:07 / 19:09≈ on time ≈ on time
19:15≈ on time ≈ on time
19:19≈ on time ≈ on time
19:25on 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 Nov— 19:24No data—
Fri 6 Nov— 19:240 min—
Thu 5 Nov— 19:24No data—
Wed 4 Nov— 19:24No data—
Tue 3 Nov— 19:24No data—
Mon 2 Nov— 19:24No data—
Sun 1 NovAmsterdam Sloterdijk 19:33Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 19:34Partial coverage0 min—
Wed 28 Oct— 19:51No data—
Tue 27 Oct— 19:33No data—
Mon 26 Oct— 19:25No data—
Sun 25 OctAmsterdam Sloterdijk 19:33No data—
Sat 24 OctAmsterdam Sloterdijk 19:34No data—
Fri 23 OctAmsterdam Sloterdijk 19:33Partial coverage+2 min+3 min
Thu 22 Oct— 19:33No data—
Wed 21 Oct— 19:27No data—
Tue 20 Oct— 19:280 min—
Mon 19 Oct— 19:26No data—
Sun 18 OctAmsterdam Sloterdijk 19:34Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 19:33Partial coverage0 min—
Fri 16 OctAmsterdam Sloterdijk 19:33No data—
Thu 15 Oct— 19:29No data—
Wed 14 OctAmsterdam Sloterdijk 19:33No data—
Tue 13 Oct— 19:27No data—
Mon 12 Oct— 19:260 min—
Fri 9 Oct— 19:270 min+1 min
Thu 8 Oct— 19:270 min—
Wed 7 Oct— 19:260 min—
Tue 6 Oct— 19:260 min—
Sat 26 SeptAmsterdam Sloterdijk 19:33No data—