Train NS 8189 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 23:35 → Hoofddorp 23:57 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November 0 min

Next service: today 23:35 from Amsterdam Centraal · Fri 6 Nov

Next departure 23:35 today · Amsterdam Centraal
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 18 full · 0 partial · 8 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 12 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: 0 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 19
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 19 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
23:35on time on time
23:40≈ on time ≈ on time
23:44≈ on time ≈ on time
23:50 / 23:53≈ on time ≈ on time
23:57on 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 Nov— 23:590 min—
Wed 4 Nov— 23:590 min—
Mon 2 Nov— 23:590 min—
Sun 1 NovSchiphol Airport 00:07+1 min+1 min
Sat 31 Oct— 23:58No data—
Fri 30 Oct— 23:580 min—
Thu 29 Oct— 23:580 min—
Wed 28 Oct— 23:580 min—
Tue 27 Oct— 23:58No data—
Mon 26 Oct— 23:58No data—
Sun 25 OctSchiphol Airport 00:070 min—
Sat 24 Oct— 23:59No data—
Fri 23 Oct— 23:590 min—
Thu 22 Oct— 23:590 min—
Wed 21 Oct— 23:580 min—
Tue 20 Oct— 23:59No data—
Mon 19 Oct— 23:580 min—
Sun 18 OctSchiphol Airport 00:070 min—
Sat 17 OctSchiphol Airport 00:07No data—
Fri 16 Oct— 23:580 min—
Thu 15 Oct— 23:590 min—
Wed 14 Oct— 23:58No data—
Tue 13 Oct— 23:59No data—
Mon 12 Oct— 23:580 min—
Fri 9 Oct— 23:580 min—
Thu 8 Oct— 23:590 min—
Wed 7 Oct— 23:580 min—
Sat 26 SeptAmsterdam Lelylaan 23:58No data—
Wed 9 SeptSchiphol Airport 00:23No data—
Sun 6 SeptSchiphol Airport 00:07No data—