Train NS 8279 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 20:48 → Hoofddorp 21:12 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:48 from Amsterdam Centraal · Sun 8 Nov

Next departure 20:48 today · Amsterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 9 full · 3 partial · 17 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 13 full · 3 partial · 25 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 Hoofddorp, 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 16 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:48on time on time
20:54 / 20:55≈ on time ≈ on time
20:59≈ on time ≈ +1 min
21:05 / 21:08≈ on time ≈ +1 min
21:12on 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 NovSchiphol Airport 21:22Partial coverage0 min—
Fri 6 Nov— 21:130 min—
Thu 5 Nov— 21:14No data—
Wed 4 Nov— 21:140 min—
Tue 3 Nov— 21:05No data—
Mon 2 Nov— 21:13+1 min+1 min
Sun 1 NovSchiphol Airport 21:22Partial coverage0 min—
Sat 31 OctSchiphol Airport 21:22No data—
Fri 30 Oct— 21:15No data—
Thu 29 Oct— 21:130 min—
Wed 28 Oct— 21:13No data—
Tue 27 Oct— 21:14No data—
Mon 26 Oct— 21:13No data—
Sun 25 OctSchiphol Airport 21:22No data—
Sat 24 OctSchiphol Airport 21:22No data—
Fri 23 Oct— 21:450 min—
Thu 22 Oct— 21:14No data—
Wed 21 Oct— 21:13No data—
Tue 20 Oct— 21:130 min—
Mon 19 Oct— 21:13No data—
Sun 18 OctSchiphol Airport 21:22Partial coverage0 min—
Sat 17 OctSchiphol Airport 21:22No data—
Fri 16 Oct— 21:130 min—
Thu 15 Oct— 21:14No data—
Wed 14 Oct— 21:13No data—
Tue 13 Oct— 21:14No data—
Mon 12 Oct— 21:130 min—
Sun 11 OctSchiphol Airport 21:22+1 min+1 min
Sat 10 Oct— 21:14No data—
Fri 9 Oct— 21:14+1 min+2 min