Train NS 8278 Hoofddorp – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 22:47 from Hoofddorp · Sat 7 Nov

Next departure 22:47 today · Hoofddorp
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 13 full · 2 partial · 13 no data
On-time · 90 days
89%
17/19 runs under 3 min
RT coverage: 17 full · 2 partial · 19 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
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

  • Wed 7 Oct Max en route +5 min · last fix heading to — +4 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 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 89% · 17
  • 3–10 min 11% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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