Train NS 8178 Hoofddorp → Amsterdam Centraal

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

NS 8178 Hoofddorp–Amsterdam Centraal: final delay under 3 min on 16 of its 19 runs with data in the last 30 days (84%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 02:04 (GMT+1).

It does not run today

Last recorded run: Friday 20 November +1 min

Next service: tomorrow 22:32 from Hoofddorp · Mon 23 Nov

Next departure 22:32 tomorrow · Hoofddorp
On-time · 30 days
84%
16/19 runs under 3 min
RT coverage: 16 full · 3 partial · 6 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 23 full · 4 partial · 20 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: +5 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

  • Fri 13 Nov Max en route +7 min · last fix heading to — +6 min
  • Mon 16 Nov Max en route +5 min · last fix heading to — +5 min
  • Wed 18 Nov Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 11% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=3
  • 80% W n=5
  • 100% T n=3
  • 83% F n=6
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 27 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
22:32on time on time
22:37 / 22:39≈ on time ≈ +1 min
22:45≈ on time ≈ +2 min
22:49≈ on time ≈ +3 min
22:55on time +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
Fri 20 Nov— 22:59+1 min+2 min
Thu 19 Nov— 22:57+1 min+1 min
Wed 18 Nov— 23:02+5 min+5 min
Tue 17 Nov— 22:540 min—
Mon 16 Nov— 23:03+5 min+5 min
Fri 13 Nov— 23:02+6 min+7 min
Thu 12 Nov— 22:570 min+1 min
Wed 11 Nov— 22:540 min—
Tue 10 Nov— 22:540 min—
Mon 9 Nov— 22:540 min—
Sun 8 NovAmsterdam Sloterdijk 23:120 min—
Sat 7 NovAmsterdam Sloterdijk 23:03Partial coverage+2 min+2 min
Fri 6 Nov— 22:540 min—
Thu 5 Nov— 23:14No data—
Wed 4 Nov— 22:59+2 min+2 min
Tue 3 Nov— 22:55No data—
Mon 2 Nov— 22:57+1 min+2 min
Sun 1 NovAmsterdam Sloterdijk 23:04Partial coverage0 min+1 min
Sat 31 OctAmsterdam Sloterdijk 23:03No data—
Fri 30 Oct— 22:56No data—
Wed 28 Oct— 22:560 min—
Tue 27 Oct— 22:59No data—
Mon 26 Oct— 22:560 min—
Sun 25 OctAmsterdam Sloterdijk 23:04No data—
Sat 24 OctSchiphol Airport 23:02Partial coverage0 min—
Fri 23 Oct— 22:560 min—
Thu 22 Oct— 22:57No data—
Wed 21 Oct— 22:59No data—
Tue 20 Oct— 22:57No data—
Mon 19 Oct— 22:56No data—