Train NS 8267 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:48 from Amsterdam Centraal · Thu 5 Nov

Next departure 17:48 today · Amsterdam Centraal
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 1 full · 11 partial · 17 no data
On-time · 90 days
92%
12/13 runs under 3 min
RT coverage: 1 full · 12 partial · 57 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

Worst days

  • Wed 7 Oct Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 12
  • 3–10 min 8% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 0% W n=1
  • 100% T n=1
  • 100% F n=2
  • 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, 13 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
17:48on time on time
17:54 / 17:55— —
17:59— —
18:05 / 18:08— —
18:12— —

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
Wed 4 NovSchiphol Airport 18:22No data—
Tue 3 NovSchiphol Airport 18:22No data—
Mon 2 NovSchiphol Airport 18:22No data—
Sun 1 NovSchiphol Airport 18:22Partial coverage0 min—
Sat 31 OctSchiphol Airport 18:22Partial coverage0 min—
Fri 30 OctSchiphol Airport 18:22No data—
Thu 29 OctAmsterdam Lelylaan 18:13No data—
Wed 28 OctSchiphol Airport 18:22No data—
Tue 27 OctAmsterdam Lelylaan 18:14No data—
Mon 26 OctSchiphol Airport 18:22Partial coverage0 min—
Sun 25 OctSchiphol Airport 18:22No data—
Sat 24 OctSchiphol Airport 18:22Partial coverage0 min—
Fri 23 OctSchiphol Airport 18:22Partial coverage0 min—
Thu 22 OctSchiphol Airport 18:22No data—
Wed 21 OctSchiphol Airport 18:22No data—
Tue 20 OctSchiphol Airport 18:22Partial coverage0 min—
Mon 19 OctSchiphol Airport 18:22No data—
Sun 18 OctSchiphol Airport 18:22Partial coverage0 min—
Sat 17 OctSchiphol Airport 18:22No data—
Fri 16 OctSchiphol Airport 18:23No data—
Thu 15 OctSchiphol Airport 18:22No data—
Wed 14 OctSchiphol Airport 18:22No data—
Tue 13 OctSchiphol Airport 18:22No data—
Mon 12 OctSchiphol Airport 18:22Partial coverage0 min—
Sun 11 OctSchiphol Airport 18:22+2 min+2 min
Sat 10 OctSchiphol Airport 18:22No data—
Fri 9 OctSchiphol Airport 18:22Partial coverage0 min—
Thu 8 OctAmsterdam Lelylaan 18:13Partial coverage0 min—
Wed 7 OctSchiphol Airport 18:22Partial coverage+3 min+3 min
Tue 6 OctAmsterdam Lelylaan 18:13Partial coverage0 min—