Train NS 8142 Hoofddorp – Amsterdam Centraal

Hoofddorp 13:32 → Amsterdam Centraal 13:55 Mon, Tue, Wed, Thu, Fri, Sat 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 20 November +1 min

Next service: Monday 13:32 from Hoofddorp · Mon 23 Nov

Next departure 13:32 Monday · Hoofddorp
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 0 full · 17 partial · 10 no data
On-time · 90 days
96%
22/23 runs under 3 min
RT coverage: 0 full · 23 partial · 54 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 Amsterdam Centraal, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 10 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +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 96% · 22
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 80% T n=5
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • 100% S n=2
  • 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
13:32on time on time
13:37 / 13:39— —
13:45— —
13:49— —
13:55— —

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
Fri 20 NovAmsterdam Sloterdijk 14:04Partial coverage+1 min+1 min
Thu 19 NovAmsterdam Sloterdijk 14:04Partial coverage0 min—
Wed 18 NovAmsterdam Sloterdijk 14:03Partial coverage0 min—
Tue 17 NovAmsterdam Sloterdijk 14:04Partial coverage+1 min+1 min
Mon 16 NovAmsterdam Sloterdijk 14:05Partial coverage0 min+1 min
Fri 13 NovAmsterdam Sloterdijk 14:04Partial coverage0 min—
Thu 12 NovAmsterdam Sloterdijk 14:03Partial coverage0 min—
Wed 11 NovAmsterdam Sloterdijk 14:04Partial coverage0 min—
Tue 10 NovAmsterdam Sloterdijk 14:04Partial coverage+3 min+3 min
Mon 9 NovAmsterdam Sloterdijk 14:04Partial coverage0 min—
Sun 8 NovAmsterdam Sloterdijk 14:03Partial coverage0 min—
Sat 7 Nov— 13:55No data—
Fri 6 NovAmsterdam Sloterdijk 14:03No data—
Thu 5 NovAmsterdam Sloterdijk 14:03No data—
Wed 4 NovAmsterdam Sloterdijk 14:03Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 14:09No data—
Mon 2 NovAmsterdam Sloterdijk 14:04No data—
Sun 1 NovAmsterdam Sloterdijk 14:05Partial coverage0 min+1 min
Sat 31 OctAmsterdam Sloterdijk 14:03Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 14:03No data—
Thu 29 OctAmsterdam Sloterdijk 14:04No data—
Wed 28 OctAmsterdam Sloterdijk 14:04Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 14:05Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 14:05No data—
Sun 25 OctAmsterdam Sloterdijk 14:04No data—
Sat 24 OctAmsterdam Sloterdijk 14:04Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 14:04No data—
Thu 22 OctAmsterdam Sloterdijk 14:04No data—
Wed 21 OctAmsterdam Sloterdijk 14:04No data—
Tue 20 OctAmsterdam Sloterdijk 14:05Partial coverage0 min—