Train NS 8451 Amsterdam Centraal → Hoofddorp

Amsterdam Centraal 13:56 → Hoofddorp 14:17 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 13:56 from Amsterdam Centraal · Sat 21 Nov

Next departure 13:56 today · Amsterdam Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 2 full · 18 partial · 9 no data
On-time · 90 days
89%
24/27 runs under 3 min
RT coverage: 4 full · 23 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 9 Oct Max en route +13 min · last fix heading to Schiphol Airport +13 min
  • Tue 10 Nov Max en route +5 min · last fix heading to Schiphol Airport +5 min
  • Sat 10 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 24
  • 3–10 min 7% · 2
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 75% T n=4
  • 100% W n=4
  • 100% T n=4
  • 75% F n=4
  • 80% S n=5
  • 100% S n=3

Stops and timetable

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

Last 90 days, 27 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:56on time on time
14:01— —
14:05— —
14:11 / 14:13— —
14:17— —

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 NovSchiphol Airport 14:27Partial coverage0 min—
Thu 19 NovSchiphol Airport 14:27Partial coverage0 min—
Wed 18 Nov— 14:18No data—
Tue 17 NovSchiphol Airport 14:27Partial coverage0 min+1 min
Mon 16 NovSchiphol Airport 14:28Partial coverage0 min—
Sun 15 NovSchiphol Airport 14:270 min—
Sat 14 NovSchiphol Airport 14:270 min—
Fri 13 NovSchiphol Airport 14:28Partial coverage+1 min+1 min
Thu 12 NovSchiphol Airport 14:28Partial coverage+2 min+3 min
Wed 11 NovSchiphol Airport 14:27Partial coverage0 min—
Tue 10 NovSchiphol Airport 14:29Partial coverage+5 min+5 min
Mon 9 NovSchiphol Airport 14:27Partial coverage0 min—
Sun 8 NovSchiphol Airport 14:30Partial coverage+2 min+3 min
Sat 7 NovSchiphol Airport 14:27Partial coverage0 min—
Fri 6 NovSchiphol Airport 14:27No data—
Thu 5 NovSchiphol Airport 14:27No data—
Wed 4 NovSchiphol Airport 14:27Partial coverage0 min—
Tue 3 NovSchiphol Airport 14:27No data—
Mon 2 NovSchiphol Airport 14:27No data—
Sun 1 NovSchiphol Airport 14:28No data—
Sat 31 OctSchiphol Airport 14:30Partial coverage+2 min+3 min
Fri 30 OctSchiphol Airport 14:27No data—
Thu 29 OctSchiphol Airport 14:30Partial coverage0 min—
Wed 28 OctSchiphol Airport 14:27Partial coverage0 min—
Tue 27 OctSchiphol Airport 14:27No data—
Mon 26 OctSchiphol Airport 14:29Partial coverage0 min—
Sun 25 OctSchiphol Airport 14:27No data—
Sat 24 OctSchiphol Airport 14:27Partial coverage0 min—
Fri 23 OctSchiphol Airport 14:27Partial coverage0 min—
Thu 22 OctSchiphol Airport 14:27No data—