Train NS 8175 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 20:05 → Hoofddorp 20:27 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 20:05 from Amsterdam Centraal · Fri 6 Nov

Next departure 20:05 today · Amsterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 10 full · 4 partial · 21 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: +1 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

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 100% · 14
  • 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=3
  • 100% T n=2
  • 100% F n=2
  • 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, 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:05on time on time
20:10≈ on time ≈ on time
20:14≈ on time ≈ on time
20:20 / 20:23≈ on time ≈ on time
20:27on 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
Thu 5 Nov— 20:29No data—
Wed 4 Nov— 20:290 min—
Tue 3 Nov— 20:29No data—
Mon 2 Nov— 20:28No data—
Sun 1 NovSchiphol Airport 20:37Partial coverage0 min—
Sat 31 OctSchiphol Airport 20:37Partial coverage0 min—
Fri 30 Oct— 20:28No data—
Thu 29 Oct— 20:280 min—
Wed 28 Oct— 20:280 min—
Tue 27 Oct— 20:290 min—
Mon 26 Oct— 20:37No data—
Sun 25 OctSchiphol Airport 20:37No data—
Sat 24 OctSchiphol Airport 20:37Partial coverage0 min—
Fri 23 Oct— 20:29+1 min+2 min
Thu 22 Oct— 20:29No data—
Wed 21 Oct— 20:29No data—
Tue 20 Oct— 20:280 min—
Mon 19 Oct— 20:28No data—
Sun 18 OctSchiphol Airport 20:37Partial coverage+1 min+1 min
Sat 17 OctSchiphol Airport 20:37No data—
Fri 16 Oct— 20:29No data—
Thu 15 Oct— 20:29No data—
Wed 14 Oct— 20:29No data—
Tue 13 Oct— 20:29No data—
Mon 12 Oct— 20:28No data—
Fri 9 Oct— 20:280 min—
Thu 8 Oct— 20:530 min—
Wed 7 Oct— 20:320 min—
Tue 6 Oct— 20:280 min—
Sat 26 SeptSchiphol Airport 20:37No data—