Train NS 8147 Amsterdam Centraal → Hoofddorp

Amsterdam Centraal 13:05 → Hoofddorp 13:27 Mon, Tue, Wed, Thu, Fri, Sat 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It does not run today

Last recorded run: Friday 20 November 0 min

Next service: Monday 13:05 from Amsterdam Centraal · Mon 23 Nov

Next departure 13:05 Monday · Amsterdam Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 0 full · 17 partial · 10 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 0 full · 22 partial · 55 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

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

  • Early 0% · 0
  • On time 100% · 22
  • 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=3
  • 100% W n=5
  • 100% T n=4
  • 100% F n=3
  • 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, 22 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:05on time on time
13:10— —
13:14— —
13:20 / 13:22— —
13:27— —

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