Train NS 8188 Hoofddorp – Amsterdam Centraal

Hoofddorp 01:02 → Amsterdam Centraal 01:25 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:28 0 min

  1. Hoofddorp01:02
  2. Schiphol Airport01:07
  3. Amsterdam Lelylaan01:15
  4. Amsterdam Sloterdijk01:19
  5. Amsterdam Centraal01:25

Next service: tomorrow 01:02 from Hoofddorp · Sun 8 Nov

Next departure 01:02 tomorrow · Hoofddorp
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 3 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 24 full · 0 partial · 7 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 Amsterdam Centraal, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
01:02on time on time
01:07 / 01:09≈ on time ≈ on time
01:15≈ on time ≈ on time
01:19≈ on time ≈ on time
01:25on 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
Sat 7 Nov— 01:280 min+1 min
Fri 6 Nov— 01:33No data—
Thu 5 Nov— 01:290 min+1 min
Wed 4 Nov— 01:140 min—
Tue 3 Nov— 01:290 min—
Mon 2 NovAmsterdam Sloterdijk 01:330 min—
Sat 31 Oct— 01:300 min—
Thu 29 Oct— 01:260 min—
Wed 28 Oct— 01:160 min—
Tue 27 Oct— 01:270 min—
Mon 26 OctAmsterdam Sloterdijk 01:340 min—
Sun 25 Oct— 01:26No data—
Sat 24 Oct— 01:270 min+1 min
Fri 23 Oct— 01:290 min—
Thu 22 Oct— 01:260 min—
Wed 21 Oct— 06:590 min—
Tue 20 Oct— 01:300 min—
Mon 19 OctAmsterdam Sloterdijk 01:330 min—
Sun 18 OctAmsterdam Sloterdijk 01:33No data—
Sat 17 Oct— 01:260 min—
Fri 16 Oct— 01:260 min—
Thu 15 Oct— 01:270 min—
Wed 14 Oct— 01:160 min—
Tue 13 Oct— 01:300 min—
Sat 10 Oct— 01:260 min—
Thu 8 Oct— 01:260 min—
Wed 7 Oct— 01:150 min—
Mon 21 SeptAmsterdam Sloterdijk 01:34No data—
Thu 10 SeptAmsterdam Sloterdijk 01:34No data—
Mon 7 SeptAmsterdam Sloterdijk 01:33No data—