Train NS 8375 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 20:13 → Hoofddorp 20:34 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Monday 16 November +5 min

Next service: today 20:13 from Amsterdam Centraal · Tue 17 Nov

Next departure 20:13 today · Amsterdam Centraal
On-time · 30 days
80%
12/15 runs under 3 min
RT coverage: 12 full · 3 partial · 12 no data
On-time · 90 days
78%
18/23 runs under 3 min
RT coverage: 20 full · 3 partial · 22 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Sat 10 Oct Max en route +14 min · last fix heading to Schiphol Airport +14 min
  • Mon 16 Nov Max en route +5 min · last fix heading to — +5 min
  • Fri 13 Nov Max en route +6 min · last fix heading to — +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to — +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 78% · 18
  • 3–10 min 17% · 4
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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:13on time on time
20:19≈ on time ≈ +1 min
20:23≈ on time ≈ +2 min
20:29 / 20:30≈ on time ≈ +4 min
20:34+1 min +5 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
Mon 16 Nov— 20:39+5 min+5 min
Sun 15 NovSchiphol Airport 20:440 min—
Sat 14 NovSchiphol Airport 20:440 min—
Fri 13 Nov— 20:39+5 min+6 min
Thu 12 Nov— 20:340 min—
Wed 11 Nov— 20:340 min—
Tue 10 Nov— 20:340 min—
Mon 9 Nov— 20:340 min—
Sat 7 NovSchiphol Airport 20:44Partial coverage0 min—
Fri 6 Nov— 20:340 min—
Wed 4 Nov— 20:38+2 min+2 min
Tue 3 Nov— 20:54No data—
Mon 2 Nov— 20:39No data—
Sun 1 NovSchiphol Airport 20:47Partial coverage+2 min+3 min
Sat 31 OctSchiphol Airport 20:47Partial coverage+3 min+3 min
Fri 30 Oct— 20:36No data—
Thu 29 Oct— 20:35+1 min+1 min
Wed 28 Oct— 20:35No data—
Tue 27 Oct— 20:38No data—
Mon 26 Oct— 20:38No data—
Sun 25 OctSchiphol Airport 20:44No data—
Sat 24 OctSchiphol Airport 20:49No data—
Fri 23 Oct— 20:40+3 min+3 min
Thu 22 Oct— 20:40No data—
Wed 21 Oct— 20:36No data—
Tue 20 Oct— 20:42No data—
Mon 19 Oct— 20:38No data—
Fri 16 Oct— 20:40No data—
Thu 15 Oct— 20:40No data—
Wed 14 Oct— 20:360 min—