Train NS 8364 Hoofddorp → Amsterdam Centraal

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

NS 8364 Hoofddorp–Amsterdam Centraal: final delay under 3 min on 20 of its 20 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 01:03 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 18:53 from Hoofddorp · Sun 22 Nov

Next departure 18:53 today · Hoofddorp
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 13 full · 7 partial · 9 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 20 full · 8 partial · 24 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 Amsterdam Centraal, 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

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

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

On-time by weekday

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

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:53on time on time
18:57 / 18:59≈ on time ≈ on time
19:05≈ on time ≈ +1 min
19:09 / 19:10≈ on time ≈ +1 min
19:17on 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
Sat 21 NovAmsterdam Sloterdijk 19:24Partial coverage0 min—
Fri 20 NovAmsterdam Sloterdijk 19:24Partial coverage0 min—
Thu 19 Nov— 19:180 min—
Wed 18 Nov— 19:190 min—
Tue 17 Nov— 19:190 min—
Mon 16 Nov— 19:17No data—
Sun 15 NovAmsterdam Sloterdijk 19:24+1 min+1 min
Sat 14 NovAmsterdam Sloterdijk 19:240 min—
Fri 13 NovHoofddorp 19:23Partial coverage+3 min+3 min
Thu 12 Nov— 19:24+2 min+2 min
Wed 11 Nov— 19:190 min—
Tue 10 Nov— 19:190 min—
Mon 9 Nov— 19:190 min—
Sun 8 NovAmsterdam Sloterdijk 19:24Partial coverage0 min—
Sat 7 NovAmsterdam Sloterdijk 19:24Partial coverage0 min—
Fri 6 Nov— 19:180 min—
Thu 5 Nov— 19:19No data—
Wed 4 Nov— 19:19No data—
Tue 3 Nov— 19:18No data—
Mon 2 Nov— 19:19+3 min+3 min
Sun 1 NovAmsterdam Sloterdijk 19:24Partial coverage+2 min+2 min
Sat 31 OctAmsterdam Sloterdijk 19:25Partial coverage+1 min—
Fri 30 OctHoofddorp 19:19No data—
Thu 29 Oct— 19:190 min+1 min
Wed 28 Oct— 19:230 min—
Tue 27 Oct— 19:21No data—
Mon 26 Oct— 19:19No data—
Sun 25 OctAmsterdam Sloterdijk 19:25No data—
Sat 24 OctAmsterdam Sloterdijk 19:25No data—
Fri 23 OctAmsterdam Sloterdijk 19:24Partial coverage0 min—