Train NS 8434 Hoofddorp – Amsterdam Centraal

Hoofddorp 11:43 → Amsterdam Centraal 12:04 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 11:43 from Hoofddorp · Thu 5 Nov

Next departure 11:43 today · Hoofddorp
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 8 full · 7 partial · 12 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 8 full · 8 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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 +5 min · last fix heading to Amsterdam Sloterdijk +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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:43on time on time
11:47 / 11:48≈ on time ≈ on time
11:54≈ on time ≈ +1 min
11:58≈ on time ≈ +1 min
12:04on time +1 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 NovAmsterdam Sloterdijk 12:13Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 12:14Partial coverage0 min—
Mon 2 NovAmsterdam Sloterdijk 12:12Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 12:150 min—
Sat 31 OctAmsterdam Sloterdijk 12:130 min—
Fri 30 OctAmsterdam Sloterdijk 12:13No data—
Thu 29 OctAmsterdam Sloterdijk 12:13Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 12:15No data—
Tue 27 OctAmsterdam Sloterdijk 12:130 min—
Mon 26 OctAmsterdam Sloterdijk 12:13No data—
Sun 25 OctAmsterdam Sloterdijk 12:13No data—
Sat 24 OctAmsterdam Sloterdijk 12:130 min—
Fri 23 OctAmsterdam Sloterdijk 12:14No data—
Thu 22 OctAmsterdam Sloterdijk 12:13No data—
Wed 21 OctAmsterdam Sloterdijk 12:13No data—
Tue 20 OctAmsterdam Sloterdijk 12:14Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 12:20No data—
Fri 16 OctAmsterdam Sloterdijk 12:13No data—
Thu 15 OctAmsterdam Sloterdijk 12:12No data—
Wed 14 OctAmsterdam Sloterdijk 12:12Partial coverage0 min—
Tue 13 OctAmsterdam Sloterdijk 12:13No data—
Mon 12 OctAmsterdam Sloterdijk 12:13No data—
Sun 11 OctAmsterdam Sloterdijk 12:16+2 min+3 min
Sat 10 OctAmsterdam Sloterdijk 12:130 min—
Fri 9 OctAmsterdam Sloterdijk 12:140 min—
Thu 8 OctAmsterdam Sloterdijk 12:14+1 min—
Wed 7 OctAmsterdam Sloterdijk 12:18Partial coverage+5 min+5 min
Tue 6 OctAmsterdam Sloterdijk 12:13Partial coverage0 min—
Fri 2 OctAmsterdam Sloterdijk 12:13No data—
Thu 1 OctAmsterdam Sloterdijk 12:13No data—