Train NS 8177 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Sunday 8 November +3 min

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

Next departure 20:26 today · Amsterdam Centraal
On-time · 30 days
90%
9/10 runs under 3 min
RT coverage: 9 full · 1 partial · 16 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 22 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: +3 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

  • Fri 23 Oct Max en route +6 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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:26on time on time
20:31 / 20:37≈ on time ≈ +1 min
20:41≈ on time ≈ +2 min
20:47 / 20:48≈ on time ≈ +2 min
20:52on time +3 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:03Partial coverage+3 min+3 min
Sat 7 Nov— 20:58No data—
Fri 6 Nov— 20:590 min—
Thu 5 Nov— 20:59No data—
Wed 4 Nov— 20:59+3 min+3 min
Tue 3 Nov— 20:58No data—
Sun 1 NovSchiphol Airport 21:070 min—
Sat 31 OctSchiphol Airport 21:07No data—
Fri 30 Oct— 20:59No data—
Wed 28 Oct— 20:580 min—
Tue 27 Oct— 21:00No data—
Mon 26 Oct— 20:59No data—
Sun 25 OctSchiphol Airport 21:07No data—
Sat 24 OctSchiphol Airport 21:08No data—
Fri 23 Oct— 21:04+5 min+6 min
Thu 22 Oct— 20:59No data—
Wed 21 Oct— 20:58No data—
Tue 20 Oct— 20:580 min—
Mon 19 Oct— 20:58No data—
Sun 18 OctSchiphol Airport 21:09+3 min+4 min
Sat 17 OctSchiphol Airport 21:07No data—
Fri 16 Oct— 20:580 min—
Thu 15 Oct— 20:59No data—
Wed 14 Oct— 20:59No data—
Tue 13 Oct— 21:07No data—
Mon 12 Oct— 20:590 min—
Fri 9 Oct— 20:58+2 min+2 min
Thu 8 Oct— 20:580 min—
Wed 7 Oct— 20:580 min—
Tue 6 Oct— 20:590 min—