Train NS 8260 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 18:17 from Hoofddorp · Thu 5 Nov

Next departure 18:17 today · Hoofddorp
On-time · 30 days
91%
10/11 runs under 3 min
RT coverage: 6 full · 5 partial · 18 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 8 full · 5 partial · 40 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

Worst days

  • Mon 2 Nov Max en route +4 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 50% M n=2
  • 100% T n=2
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • — 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, 13 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
18:17on time +1 min
18:21 / 18:22≈ on time ≈ +2 min
18:29≈ on time ≈ +2 min
18:33≈ on time ≈ +2 min
18:39on time +2 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
Wed 4 Nov— 18:39No data—
Tue 3 Nov— 18:39No data—
Mon 2 Nov— 18:44+4 min+4 min
Sun 1 NovAmsterdam Sloterdijk 18:47Partial coverage+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 18:47No data—
Fri 30 OctAmsterdam Sloterdijk 18:47No data—
Thu 29 Oct— 18:40No data—
Wed 28 Oct— 18:410 min—
Tue 27 Oct— 18:41No data—
Mon 26 Oct— 18:40No data—
Sun 25 OctAmsterdam Sloterdijk 18:47No data—
Sat 24 OctAmsterdam Sloterdijk 18:49No data—
Fri 23 OctAmsterdam Sloterdijk 18:47Partial coverage+1 min+1 min
Thu 22 OctAmsterdam Sloterdijk 18:47No data—
Wed 21 OctAmsterdam Sloterdijk 18:47No data—
Tue 20 OctAmsterdam Sloterdijk 18:47Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 18:47No data—
Sun 18 OctAmsterdam Sloterdijk 18:47Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 18:47No data—
Fri 16 OctAmsterdam Sloterdijk 18:51No data—
Thu 15 OctAmsterdam Lelylaan 18:45No data—
Wed 14 OctAmsterdam Sloterdijk 18:48No data—
Tue 13 OctAmsterdam Sloterdijk 18:48No data—
Mon 12 OctAmsterdam Sloterdijk 18:480 min—
Sun 11 OctAmsterdam Sloterdijk 18:48+1 min—
Sat 10 OctHoofddorp 18:40No data—
Fri 9 OctAmsterdam Sloterdijk 18:47Partial coverage0 min—
Thu 8 Oct— 18:410 min—
Wed 7 Oct— 18:400 min—
Tue 6 Oct— 18:400 min—