Train NS 8239 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 10:48 → Hoofddorp 11:12 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 11:22 0 min

  1. Amsterdam Centraal10:48
  2. Amsterdam Sloterdijk10:54
  3. Amsterdam Lelylaan10:59
  4. Schiphol Airport11:05
  5. Hoofddorp11:12

Next service: tomorrow 10:48 from Amsterdam Centraal · Fri 6 Nov

Next departure 10:48 tomorrow · Amsterdam Centraal
On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 2 full · 15 partial · 13 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 11 full · 16 partial · 44 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Sun 18 Oct Max en route +8 min · last fix heading to Schiphol Airport +8 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 96% · 26
  • 3–10 min 4% · 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
  • 100% T n=4
  • 100% F n=3
  • 100% S n=3
  • 75% S n=4

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
10:48on time on time
10:54 / 10:55≈ on time ≈ on time
10:59≈ on time ≈ on time
11:05 / 11:08≈ on time ≈ on time
11:12on 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
Thu 5 NovSchiphol Airport 11:22Partial coverage0 min—
Wed 4 NovSchiphol Airport 11:22Partial coverage0 min—
Tue 3 NovSchiphol Airport 11:22Partial coverage0 min—
Mon 2 NovSchiphol Airport 11:22No data—
Sun 1 NovSchiphol Airport 11:22Partial coverage0 min—
Sat 31 OctSchiphol Airport 11:22Partial coverage0 min—
Fri 30 OctSchiphol Airport 11:24No data—
Thu 29 OctSchiphol Airport 11:22Partial coverage0 min—
Wed 28 OctSchiphol Airport 11:22No data—
Tue 27 OctSchiphol Airport 11:22No data—
Mon 26 OctSchiphol Airport 11:22No data—
Sun 25 OctSchiphol Airport 11:22No data—
Sat 24 OctSchiphol Airport 11:22Partial coverage0 min—
Fri 23 OctSchiphol Airport 11:22Partial coverage0 min—
Thu 22 OctSchiphol Airport 11:22No data—
Wed 21 OctSchiphol Airport 11:25No data—
Tue 20 OctSchiphol Airport 11:22Partial coverage0 min—
Mon 19 OctSchiphol Airport 11:22No data—
Sun 18 OctSchiphol Airport 11:29Partial coverage+8 min+8 min
Sat 17 OctSchiphol Airport 11:22No data—
Fri 16 OctSchiphol Airport 11:22No data—
Thu 15 OctSchiphol Airport 11:22No data—
Wed 14 OctSchiphol Airport 11:22Partial coverage0 min—
Tue 13 OctSchiphol Airport 11:22No data—
Mon 12 OctSchiphol Airport 11:22Partial coverage0 min—
Sun 11 OctSchiphol Airport 11:220 min—
Sat 10 OctSchiphol Airport 11:220 min—
Fri 9 OctSchiphol Airport 11:22Partial coverage+1 min+1 min
Thu 8 OctSchiphol Airport 11:22Partial coverage0 min—
Wed 7 OctAmsterdam Sloterdijk 12:05Partial coverage0 min—