Train NS 8182 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

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

Next departure 23:32 today · Hoofddorp
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 11 full · 2 partial · 14 no data
On-time · 90 days
100%
17/17 runs under 3 min
RT coverage: 15 full · 2 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

  • Early 0% · 0
  • On time 100% · 17
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 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=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, 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
23:32on time on time
23:37 / 23:39≈ on time ≈ on time
23:45≈ on time ≈ on time
23:49≈ on time ≈ on time
23:55on time +1 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
Sat 7 Nov— 23:540 min—
Fri 6 Nov— 23:540 min—
Thu 5 Nov— 23:54No data—
Wed 4 Nov— 23:54+1 min+1 min
Tue 3 Nov— 23:54No data—
Mon 2 Nov— 23:570 min—
Sun 1 NovAmsterdam Sloterdijk 00:04Partial coverage0 min+1 min
Sat 31 Oct— 23:58No data—
Fri 30 Oct— 23:56No data—
Thu 29 Oct— 23:560 min+1 min
Wed 28 Oct— 23:56No data—
Tue 27 Oct— 23:560 min—
Mon 26 Oct— 23:56No data—
Sun 25 OctAmsterdam Sloterdijk 00:04No data—
Sat 24 Oct— 23:590 min—
Fri 23 Oct— 23:570 min+1 min
Thu 22 Oct— 23:55No data—
Wed 21 Oct— 23:56No data—
Tue 20 Oct— 23:59No data—
Mon 19 Oct— 23:570 min+1 min
Sun 18 OctAmsterdam Sloterdijk 00:03Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 00:03No data—
Fri 16 Oct— 23:56No data—
Thu 15 Oct— 00:02No data—
Wed 14 Oct— 23:560 min—
Tue 13 Oct— 23:56No data—
Mon 12 Oct— 23:560 min—
Fri 9 Oct— 23:560 min—
Thu 8 Oct— 23:560 min—
Wed 7 Oct— 23:550 min—