Train NS 8271 Amsterdam Centraal → Hoofddorp

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

It has not run yet today

Last recorded run: Friday 20 November 0 min

Next service: today 18:48 from Amsterdam Centraal · Sat 21 Nov

Next departure 18:48 today · Amsterdam Centraal
On-time · 30 days
81%
17/21 runs under 3 min
RT coverage: 15 full · 6 partial · 8 no data
On-time · 90 days
82%
23/28 runs under 3 min
RT coverage: 21 full · 7 partial · 33 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+6min
9 in 10 runs arrive with less than this
30 days: +6 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

Worst days

  • Wed 18 Nov Max en route +9 min · last fix heading to — +9 min
  • Mon 16 Nov Max en route +9 min · last fix heading to — +9 min
  • Sun 15 Nov Max en route +6 min · last fix heading to Schiphol Airport +6 min
  • Tue 10 Nov Max en route +6 min · last fix heading to — +6 min
  • Sun 11 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 82% · 23
  • 3–10 min 18% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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