Train NS 8142 Hoofddorp – Amsterdam Centraal

Hoofddorp 13:32 → Amsterdam Centraal 13:55 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 14:03 No data

  1. Hoofddorp13:32
  2. Schiphol Airport13:37
  3. Amsterdam Lelylaan13:45
  4. Amsterdam Sloterdijk13:49
  5. Amsterdam Centraal13:55

Next service: tomorrow 13:32 from Hoofddorp · Fri 6 Nov

Next departure 13:32 tomorrow · Hoofddorp
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 17 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 full · 12 partial · 56 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 Amsterdam Centraal, 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

  • — M n=0
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=1
  • 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
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
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—
Mon 19 OctAmsterdam Sloterdijk 14:04No data—
Sun 18 OctAmsterdam Sloterdijk 14:03Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 14:04No data—
Fri 16 OctAmsterdam Sloterdijk 14:04No data—
Thu 15 OctAmsterdam Sloterdijk 14:04No data—
Wed 14 OctAmsterdam Sloterdijk 14:04No data—
Tue 13 OctAmsterdam Sloterdijk 14:03No data—
Mon 12 OctAmsterdam Sloterdijk 14:03No data—
Fri 9 OctAmsterdam Sloterdijk 14:04Partial coverage0 min—
Thu 8 OctAmsterdam Sloterdijk 14:03Partial coverage0 min+1 min
Wed 7 OctAmsterdam Sloterdijk 14:03Partial coverage0 min—
Tue 6 OctAmsterdam Sloterdijk 14:04Partial coverage0 min+1 min
Fri 2 OctAmsterdam Sloterdijk 14:04No data—