Train NS 8149 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 13:35 → Hoofddorp 13:57 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:35 from Amsterdam Centraal · Sat 7 Nov

Next departure 13:35 today · Amsterdam Centraal
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 18 no data
On-time · 90 days
100%
12/12 runs under 3 min
RT coverage: 0 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: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 12 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
13:35on time on time
13:40— —
13:44— —
13:50 / 13:53— —
13:57— —

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