Train NS 8151 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 14:05 → Hoofddorp 14:27 Mon, Tue, Wed, Thu, Fri 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 14:37 +1 min

  1. Amsterdam Centraal14:05
  2. Amsterdam Sloterdijk14:10
  3. Amsterdam Lelylaan14:14
  4. Schiphol Airport14:20
  5. Hoofddorp14:27

Next service: tomorrow 14:05 from Amsterdam Centraal · Thu 19 Nov

Next departure 14:05 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 0 full · 16 partial · 12 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 0 full · 22 partial · 53 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: +3 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

  • Thu 12 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 50% T n=2
  • 100% F n=2
  • 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, 22 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
14:05on time on time
14:10— —
14:14— —
14:20 / 14:23— —
14:27— —

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