Train NS 8179 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 20:56 → Hoofddorp 21:22 Daily 0 h 26 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Sunday 8 November +4 min

Next service: today 20:56 from Amsterdam Centraal · Mon 9 Nov

Next departure 20:56 today · Amsterdam Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 14 no data
On-time · 90 days
94%
17/18 runs under 3 min
RT coverage: 17 full · 1 partial · 20 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

  • Sun 8 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 17
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
20:56on time on time
21:01 / 21:07≈ on time ≈ on time
21:11≈ on time ≈ +1 min
21:17 / 21:18≈ on time ≈ +1 min
21:22on 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
Sun 8 NovSchiphol Airport 21:34Partial coverage+4 min+4 min
Sat 7 NovSchiphol Airport 21:39+2 min+3 min
Fri 6 Nov— 21:29+2 min+2 min
Thu 5 Nov— 21:29No data—
Wed 4 Nov— 21:29+1 min+1 min
Tue 3 Nov— 21:20No data—
Mon 2 Nov— 21:280 min—
Sun 1 NovSchiphol Airport 21:370 min—
Sat 31 OctSchiphol Airport 21:37No data—
Fri 30 Oct— 21:28No data—
Thu 29 Oct— 21:28+1 min+1 min
Wed 28 Oct— 22:020 min—
Tue 27 Oct— 21:300 min—
Mon 26 Oct— 21:28No data—
Sun 25 OctSchiphol Airport 21:37No data—
Sat 24 OctSchiphol Airport 21:370 min—
Fri 23 Oct— 21:280 min—
Thu 22 Oct— 21:13No data—
Wed 21 Oct— 21:29No data—
Tue 20 Oct— 21:280 min—
Mon 19 Oct— 21:28No data—
Sun 18 OctSchiphol Airport 21:38+1 min—
Sat 17 OctSchiphol Airport 21:37No data—
Fri 16 Oct— 21:280 min—
Thu 15 Oct— 21:28No data—
Wed 14 Oct— 21:33No data—
Tue 13 Oct— 21:28No data—
Mon 12 Oct— 21:28No data—
Fri 9 Oct— 21:29+1 min+1 min
Thu 8 Oct— 21:280 min—