Train NS 8225 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 07:18 → Hoofddorp 07:42 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 07:52 0 min

  1. Amsterdam Centraal07:18
  2. Amsterdam Sloterdijk07:24
  3. Amsterdam Lelylaan07:29
  4. Schiphol Airport07:35
  5. Hoofddorp07:42

Next service: tomorrow 07:18 from Amsterdam Centraal · Mon 9 Nov

Next departure 07:18 tomorrow · Amsterdam Centraal
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 3 full · 16 partial · 11 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 10 full · 20 partial · 45 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: +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

  • Sun 1 Nov Max en route +8 min · last fix heading to Schiphol Airport +7 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=4
  • 100% T n=4
  • 100% F n=5
  • 100% S n=4
  • 50% S n=4

Stops and timetable

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

Last 90 days, 30 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
07:18on time on time
07:24 / 07:25≈ on time ≈ +2 min
07:29≈ on time ≈ +3 min
07:35 / 07:38≈ on time ≈ +4 min
07:42on time +6 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
Sun 8 NovSchiphol Airport 07:52Partial coverage0 min—
Sat 7 NovSchiphol Airport 07:52Partial coverage+2 min+2 min
Fri 6 NovSchiphol Airport 07:52No data—
Thu 5 NovSchiphol Airport 07:59No data—
Wed 4 NovSchiphol Airport 07:52Partial coverage+1 min+2 min
Tue 3 NovSchiphol Airport 07:52No data—
Mon 2 NovSchiphol Airport 07:52No data—
Sun 1 NovSchiphol Airport 07:59+7 min+8 min
Sat 31 OctSchiphol Airport 07:52No data—
Fri 30 OctSchiphol Airport 07:52Partial coverage0 min—
Thu 29 OctSchiphol Airport 07:52Partial coverage0 min—
Wed 28 OctSchiphol Airport 07:52Partial coverage0 min—
Tue 27 OctSchiphol Airport 07:52Partial coverage0 min—
Mon 26 OctSchiphol Airport 07:52Partial coverage0 min—
Sun 25 OctSchiphol Airport 07:52No data—
Sat 24 OctSchiphol Airport 07:52Partial coverage0 min—
Fri 23 OctSchiphol Airport 07:52Partial coverage0 min—
Thu 22 OctSchiphol Airport 07:52Partial coverage0 min—
Wed 21 OctSchiphol Airport 07:52No data—
Tue 20 OctSchiphol Airport 07:52Partial coverage0 min—
Mon 19 OctSchiphol Airport 07:52Partial coverage0 min—
Sun 18 OctSchiphol Airport 07:55Partial coverage+3 min+4 min
Sat 17 OctSchiphol Airport 07:52Partial coverage+1 min+1 min
Fri 16 OctSchiphol Airport 07:52Partial coverage0 min—
Thu 15 OctSchiphol Airport 07:52No data—
Wed 14 OctSchiphol Airport 07:52No data—
Tue 13 OctSchiphol Airport 07:52No data—
Mon 12 OctSchiphol Airport 07:52No data—
Sun 11 OctSchiphol Airport 07:52+5 min+5 min
Sat 10 OctSchiphol Airport 07:520 min—