Train NS 8237 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 10:20 → Hoofddorp 10:42 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 10:53 +4 min

  1. Amsterdam Centraal10:20
  2. Amsterdam Sloterdijk10:25
  3. Amsterdam Lelylaan10:29
  4. Schiphol Airport10:35
  5. Hoofddorp10:42

Next service: tomorrow 10:20 from Amsterdam Centraal · Mon 16 Nov

Next departure 10:20 tomorrow · Amsterdam Centraal
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 19 full · 1 partial · 10 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 33 full · 1 partial · 47 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 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

  • Wed 9 Sept Max en route +38 min · last fix heading to Schiphol Airport +33 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=6
  • 83% W n=6
  • 100% T n=4
  • 100% F n=4
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 34 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
10:20on time on time
10:25≈ on time ≈ on time
10:29≈ on time ≈ +1 min
10:35 / 10:38≈ on time ≈ on time
10:42on time on time

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