Train NS 8475 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 19:56 from Amsterdam Centraal · Fri 6 Nov

Next departure 19:56 today · Amsterdam Centraal
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 8 full · 2 partial · 15 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 10 full · 2 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 12
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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