Train NS 8184 Hoofddorp – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to — at 00:27 0 min

  1. Hoofddorp00:02
  2. Schiphol Airport00:07
  3. Amsterdam Lelylaan00:15
  4. Amsterdam Sloterdijk00:19
  5. Amsterdam Centraal00:25

Next service: tomorrow 00:02 from Hoofddorp · Sat 7 Nov

Next departure 00:02 tomorrow · Hoofddorp
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 2 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 5 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

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

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

On-time by weekday

  • — M n=0
  • 100% T n=3
  • 100% W n=4
  • 100% T n=5
  • 100% F n=4
  • 100% S n=4
  • 100% S n=2

Stops and timetable

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

Last 90 days, 22 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
00:02on time on time
00:07 / 00:09≈ on time ≈ on time
00:15≈ on time ≈ on time
00:19≈ on time ≈ on time
00: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
Fri 6 Nov— 00:270 min—
Thu 5 Nov— 00:270 min—
Wed 4 Nov— 00:270 min—
Sun 1 NovAmsterdam Sloterdijk 00:330 min—
Sat 31 Oct— 00:270 min—
Fri 30 Oct— 00:290 min—
Thu 29 Oct— 00:260 min—
Wed 28 Oct— 00:250 min—
Tue 27 Oct— 00:260 min—
Sun 25 OctAmsterdam Sloterdijk 00:33No data—
Sat 24 Oct— 00:270 min—
Fri 23 Oct— 00:260 min—
Thu 22 Oct— 00:260 min—
Wed 21 Oct— 00:26No data—
Tue 20 Oct— 00:290 min+1 min
Sun 18 OctAmsterdam Sloterdijk 00:330 min—
Sat 17 OctAmsterdam Sloterdijk 00:330 min—
Fri 16 Oct— 00:260 min—
Thu 15 Oct— 00:260 min—
Wed 14 Oct— 00:250 min—
Tue 13 Oct— 00:260 min—
Sat 10 Oct— 00:26+1 min+1 min
Thu 8 Oct— 00:310 min—
Wed 7 Oct— 00:250 min—
Thu 10 SeptAmsterdam Sloterdijk 00:44No data—
Sun 6 SeptAmsterdam Sloterdijk 00:34No data—
Sun 30 AugAmsterdam Sloterdijk 00:35No data—