Train NS 8369 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 18:43 → Hoofddorp 19:04 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 18:43 from Amsterdam Centraal · Fri 6 Nov

Next departure 18:43 today · Amsterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 7 full · 5 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 9 full · 5 partial · 42 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

  • Early 0% · 0
  • On time 100% · 14
  • 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=2
  • 100% S n=2
  • 100% S n=2

Stops and timetable

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

Last 90 days, 14 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:43on time on time
18:48≈ on time ≈ +1 min
18:52≈ on time ≈ +1 min
18:58 / 19:00≈ on time ≈ +1 min
19:04on 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
Thu 5 Nov— 19:22No data—
Wed 4 Nov— 19:04No data—
Tue 3 Nov— 19:05No data—
Mon 2 Nov— 19:040 min—
Sun 1 NovSchiphol Airport 19:14Partial coverage+2 min+3 min
Sat 31 OctSchiphol Airport 19:14Partial coverage0 min—
Fri 30 OctAmsterdam Lelylaan 19:09No data—
Thu 29 Oct— 19:06+1 min+2 min
Wed 28 Oct— 19:260 min—
Tue 27 Oct— 19:06No data—
Mon 26 Oct— 19:06No data—
Sun 25 OctSchiphol Airport 19:15No data—
Sat 24 OctSchiphol Airport 19:17No data—
Fri 23 OctSchiphol Airport 19:14Partial coverage+3 min+3 min
Thu 22 OctAmsterdam Centraal 19:06No data—
Wed 21 Oct— 19:07No data—
Tue 20 OctAmsterdam Centraal 19:06Partial coverage0 min—
Mon 19 OctAmsterdam Centraal 19:08No data—
Fri 16 OctSchiphol Airport 19:14No data—
Thu 15 Oct— 19:07No data—
Wed 14 OctSchiphol Airport 19:09No data—
Tue 13 Oct— 19:06No data—
Mon 12 OctAmsterdam Centraal 19:06Partial coverage0 min—
Sun 11 OctSchiphol Airport 19:140 min—
Sat 10 OctSchiphol Airport 19:15+1 min+1 min
Fri 9 Oct— 19:060 min+1 min
Thu 8 Oct— 19:06+1 min—
Wed 7 Oct— 19:050 min—
Tue 6 Oct— 19:08+1 min+2 min
Fri 2 OctAmsterdam Sloterdijk 19:02No data—