Train NS 8425 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 07:26 → Hoofddorp 07:47 Mon, Tue, Wed, Thu, Fri 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 07:26 from Amsterdam Centraal · Mon 9 Nov

Next departure 07:26 Monday · Amsterdam Centraal
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 8 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 1 full · 15 partial · 48 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Mon 26 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 67% M n=3
  • 100% T n=2
  • 100% W n=4
  • 100% T n=3
  • 100% F n=4
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 16 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:26on time on time
07:31— —
07:35— —
07:41 / 07:43— —
07:47— —

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 6 NovSchiphol Airport 07:57No data—
Thu 5 NovSchiphol Airport 07:57No data—
Wed 4 NovSchiphol Airport 07:57Partial coverage0 min+1 min
Tue 3 NovSchiphol Airport 07:57No data—
Mon 2 NovSchiphol Airport 07:57Partial coverage0 min—
Fri 30 OctSchiphol Airport 07:57Partial coverage0 min—
Thu 29 OctSchiphol Airport 07:58Partial coverage+1 min+1 min
Wed 28 OctSchiphol Airport 07:58Partial coverage0 min—
Tue 27 OctSchiphol Airport 08:03No data—
Mon 26 OctSchiphol Airport 08:02Partial coverage+5 min+5 min
Fri 23 OctSchiphol Airport 07:57Partial coverage0 min—
Thu 22 OctSchiphol Airport 07:58Partial coverage0 min—
Wed 21 OctSchiphol Airport 07:57No data—
Tue 20 OctSchiphol Airport 07:570 min—
Mon 19 OctSchiphol Airport 07:57Partial coverage0 min—
Fri 16 OctSchiphol Airport 08:02Partial coverage0 min—
Thu 15 OctSchiphol Airport 07:57No data—
Wed 14 OctSchiphol Airport 07:57Partial coverage0 min—
Tue 13 OctSchiphol Airport 07:57No data—
Mon 12 OctSchiphol Airport 07:57No data—
Fri 9 OctSchiphol Airport 07:57Partial coverage0 min—
Thu 8 OctSchiphol Airport 07:57Partial coverage0 min—
Wed 7 OctSchiphol Airport 07:57Partial coverage0 min—
Tue 6 OctSchiphol Airport 07:58Partial coverage+1 min+2 min
Fri 2 OctSchiphol Airport 07:57No data—
Thu 1 OctSchiphol Airport 07:58No data—
Wed 30 SeptSchiphol Airport 08:02No data—
Tue 29 SeptSchiphol Airport 07:57No data—
Mon 28 SeptSchiphol Airport 07:57No data—
Fri 25 SeptSchiphol Airport 07:57No data—