Train NS 8268 Hoofddorp – Amsterdam Centraal

Hoofddorp 20:17 → Amsterdam Centraal 20:39 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 20:48 0 min

  1. Hoofddorp20:17
  2. Schiphol Airport20:21
  3. Amsterdam Lelylaan20:29
  4. Amsterdam Sloterdijk20:33
  5. Amsterdam Centraal20:39

Next service: tomorrow 20:17 from Hoofddorp · Sun 8 Nov

Next departure 20:17 tomorrow · Hoofddorp
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 7 full · 3 partial · 19 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 26 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 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=1
  • 100% W n=2
  • 100% T n=2
  • 100% F n=3
  • 100% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 14 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
20:17on time on time
20:21 / 20:22≈ on time ≈ on time
20:29≈ on time ≈ +1 min
20:33≈ on time ≈ +1 min
20:39on time +1 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
Sat 7 NovAmsterdam Sloterdijk 20:48Partial coverage0 min—
Fri 6 Nov— 20:420 min+1 min
Thu 5 Nov— 20:39No data—
Wed 4 Nov— 20:44+3 min+3 min
Tue 3 Nov— 20:39No data—
Mon 2 Nov— 20:39No data—
Sun 1 NovAmsterdam Sloterdijk 20:48Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 20:47No data—
Fri 30 Oct— 20:46No data—
Thu 29 Oct— 20:400 min—
Wed 28 Oct— 20:45No data—
Tue 27 Oct— 20:41No data—
Mon 26 Oct— 20:40No data—
Sun 25 OctAmsterdam Sloterdijk 20:47No data—
Sat 24 OctAmsterdam Sloterdijk 20:49No data—
Fri 23 Oct— 20:400 min—
Thu 22 Oct— 20:41No data—
Wed 21 Oct— 20:40No data—
Mon 19 Oct— 20:41No data—
Sun 18 OctAmsterdam Sloterdijk 20:47Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 20:48No data—
Fri 16 Oct— 20:41No data—
Thu 15 Oct— 20:45No data—
Wed 14 Oct— 20:40No data—
Tue 13 Oct— 20:45No data—
Mon 12 Oct— 20:450 min—
Sun 11 OctAmsterdam Sloterdijk 20:480 min—
Sat 10 Oct— 20:41No data—
Fri 9 Oct— 20:420 min—
Thu 8 Oct— 20:480 min—