Train NS 8134 Hoofddorp – Amsterdam Centraal

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

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 12:04 No data

  1. Hoofddorp11:32
  2. Schiphol Airport11:37
  3. Amsterdam Lelylaan11:45
  4. Amsterdam Sloterdijk11:49
  5. Amsterdam Centraal11:55

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

Next departure 11:32 tomorrow · Hoofddorp
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 0 full · 11 partial · 17 no data
On-time · 90 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 56 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Wed 7 Oct Max en route +17 min · last fix heading to Amsterdam Sloterdijk +17 min

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 92% · 11
  • 3–10 min 0% · 0
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=3
  • 67% 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
11:32on time on time
11:37 / 11:39— —
11:45— —
11:49— —
11: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 12:04No data—
Wed 4 NovAmsterdam Sloterdijk 12:04Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 12:04No data—
Mon 2 NovAmsterdam Sloterdijk 12:04No data—
Sun 1 NovAmsterdam Sloterdijk 12:05Partial coverage+1 min—
Sat 31 OctAmsterdam Sloterdijk 12:04Partial coverage+1 min—
Fri 30 OctAmsterdam Sloterdijk 12:07No data—
Thu 29 OctAmsterdam Sloterdijk 12:04No data—
Wed 28 OctAmsterdam Sloterdijk 12:04Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 12:04Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 12:04No data—
Sun 25 OctAmsterdam Sloterdijk 12:05No data—
Sat 24 OctAmsterdam Sloterdijk 12:04Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 12:05No data—
Thu 22 OctAmsterdam Sloterdijk 12:05No data—
Wed 21 OctAmsterdam Sloterdijk 12:03No data—
Tue 20 OctAmsterdam Sloterdijk 12:03Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 12:04No data—
Sun 18 OctAmsterdam Sloterdijk 12:05Partial coverage+1 min+2 min
Sat 17 OctAmsterdam Sloterdijk 12:04No data—
Fri 16 OctAmsterdam Sloterdijk 12:04No data—
Thu 15 OctAmsterdam Sloterdijk 12:04No data—
Wed 14 OctAmsterdam Sloterdijk 12:04No data—
Tue 13 OctAmsterdam Sloterdijk 12:04No data—
Mon 12 OctAmsterdam Sloterdijk 12:05No data—
Fri 9 OctAmsterdam Sloterdijk 12:04Partial coverage+1 min—
Thu 8 OctAmsterdam Sloterdijk 12:04Partial coverage+2 min+3 min
Wed 7 OctAmsterdam Sloterdijk 12:21Partial coverage+17 min+17 min
Tue 6 OctAmsterdam Sloterdijk 12:04Partial coverage0 min—
Fri 2 OctAmsterdam Sloterdijk 12:04No data—