Train NS 8270 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:47 from Hoofddorp · Sun 8 Nov

Next departure 20:47 today · Hoofddorp
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 11 full · 4 partial · 14 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 22 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: +2 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

  • Fri 23 Oct Max en route +9 min · last fix heading to — +9 min

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 95% · 18
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 75% F n=4
  • 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, 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
20:47on time +1 min
20:51 / 20:53≈ on time ≈ +2 min
20:59≈ on time ≈ +1 min
21:03≈ on time ≈ +1 min
21:09on 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 21:17Partial coverage0 min—
Fri 6 Nov— 21:090 min—
Thu 5 Nov— 21:09No data—
Wed 4 Nov— 21:090 min—
Tue 3 Nov— 21:100 min—
Mon 2 Nov— 21:14+2 min+3 min
Sun 1 NovAmsterdam Sloterdijk 21:17Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 21:18No data—
Fri 30 Oct— 21:11No data—
Thu 29 Oct— 21:100 min—
Wed 28 Oct— 21:10No data—
Tue 27 Oct— 21:11No data—
Mon 26 Oct— 21:100 min—
Sun 25 OctAmsterdam Sloterdijk 21:18No data—
Sat 24 OctAmsterdam Sloterdijk 21:18Partial coverage0 min—
Fri 23 Oct— 21:24+9 min+9 min
Thu 22 Oct— 21:110 min—
Wed 21 Oct— 21:10No data—
Tue 20 Oct— 21:13No data—
Mon 19 Oct— 21:11No data—
Sun 18 OctAmsterdam Sloterdijk 21:19Partial coverage+1 min+2 min
Sat 17 OctAmsterdam Sloterdijk 21:18No data—
Fri 16 Oct— 21:100 min—
Thu 15 Oct— 21:13No data—
Wed 14 Oct— 21:11No data—
Tue 13 Oct— 21:11No data—
Mon 12 Oct— 21:100 min—
Sun 11 OctAmsterdam Sloterdijk 21:170 min—
Sat 10 Oct— 21:13No data—
Fri 9 Oct— 21:150 min+2 min