Train NS 8262 Hoofddorp → Amsterdam Centraal

Hoofddorp 18:47 → Amsterdam Centraal 19:09 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 18:47 from Hoofddorp · Sat 21 Nov

Next departure 18:47 today · Hoofddorp
On-time · 30 days
90%
18/20 runs under 3 min
RT coverage: 11 full · 9 partial · 8 no data
On-time · 90 days
93%
28/30 runs under 3 min
RT coverage: 20 full · 10 partial · 30 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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 16 Nov Max en route +28 min · last fix heading to — +27 min
  • Wed 18 Nov Max en route +4 min · last fix heading to — +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 28
  • 3–10 min 3% · 1
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 75% M n=4
  • 100% T n=3
  • 75% W n=4
  • 100% T n=4
  • 100% F n=6
  • 100% S n=4
  • 100% S n=5

Stops and timetable

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

Last 90 days, 30 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:47on time on time
18:51 / 18:53≈ on time ≈ on time
18:59≈ on time ≈ +1 min
19:03≈ on time ≈ +2 min
19:09on 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
Fri 20 NovAmsterdam Sloterdijk 19:17Partial coverage0 min—
Thu 19 Nov— 19:090 min—
Wed 18 Nov— 19:14+3 min+4 min
Tue 17 Nov— 19:14+2 min+3 min
Mon 16 Nov— 19:39+27 min+28 min
Sun 15 NovAmsterdam Sloterdijk 19:18+2 min+2 min
Sat 14 NovAmsterdam Sloterdijk 19:17No data—
Fri 13 NovSchiphol Airport 19:09Partial coverage0 min—
Thu 12 Nov— 19:14+2 min+3 min
Wed 11 Nov— 19:090 min—
Tue 10 Nov— 19:090 min—
Mon 9 Nov— 19:090 min—
Sun 8 NovAmsterdam Sloterdijk 19:18Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 19:17Partial coverage0 min—
Fri 6 NovHoofddorp 19:09Partial coverage0 min—
Thu 5 Nov— 19:09No data—
Wed 4 Nov— 19:09No data—
Tue 3 Nov— 19:09No data—
Mon 2 Nov— 19:090 min—
Sun 1 NovAmsterdam Sloterdijk 19:18Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 19:18Partial coverage0 min—
Fri 30 OctSchiphol Airport 19:10No data—
Wed 28 Oct— 20:150 min—
Tue 27 Oct— 19:11No data—
Mon 26 Oct— 19:13No data—
Sun 25 OctAmsterdam Sloterdijk 19:18No data—
Sat 24 OctAmsterdam Sloterdijk 19:17Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 19:16Partial coverage+3 min+3 min
Thu 22 Oct— 19:110 min—
Wed 21 Oct— 19:11No data—