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: Wednesday 4 November +2 min

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

Next departure 20:13 today · Amsterdam Centraal
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 9 full · 2 partial · 15 no data
On-time · 90 days
77%
10/13 runs under 3 min
RT coverage: 11 full · 2 partial · 28 no data
Typical delay
+2min
Median at arrival, 90 days
30 days: +2 min
P90
+4min
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

  • Sat 10 Oct Max en route +14 min · last fix heading to Schiphol Airport +14 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

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

  • Early 0% · 0
  • On time 77% · 10
  • 3–10 min 15% · 2
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 0% T n=1
  • 100% W n=3
  • 100% T n=2
  • 50% F n=2
  • 50% 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, 13 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≈ +1 min ≈ +2 min
20:29 / 20:30≈ +1 min ≈ +3 min
20:34+2 min +4 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
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—
Tue 13 Oct— 20:36No data—
Mon 12 Oct— 20:350 min—
Sun 11 OctSchiphol Airport 20:46+2 min+2 min
Sat 10 OctSchiphol Airport 20:56+14 min+14 min
Fri 9 Oct— 20:360 min—
Thu 8 Oct— 20:40+2 min+2 min
Wed 7 Oct— 20:38+1 min+1 min
Tue 6 Oct— 20:40+4 min+4 min
Sat 26 SeptSchiphol Airport 20:45No data—
Sun 20 SeptSchiphol Airport 20:46No data—