Train NS 8370 Hoofddorp → Amsterdam Centraal

Hoofddorp 20:23 → Amsterdam Centraal 20:46 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

NS 8370 Hoofddorp–Amsterdam Centraal: final delay under 3 min on 18 of its 19 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 10:58 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 20:23 from Hoofddorp · Sun 22 Nov

Next departure 20:23 today · Hoofddorp
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 15 full · 4 partial · 8 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 23 full · 4 partial · 21 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

Worst days

  • Fri 13 Nov Max en route +6 min · last fix heading to — +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 27 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
20:23on time on time
20:27 / 20:29≈ on time ≈ +1 min
20:35≈ on time ≈ +1 min
20:39 / 20:40≈ on time ≈ +2 min
20:46on time +2 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 20:54Partial coverage0 min—
Fri 20 Nov— 20:480 min—
Thu 19 Nov— 20:480 min—
Wed 18 Nov— 20:480 min+2 min
Tue 17 Nov— 20:480 min—
Mon 16 Nov— 20:48+1 min+9 min
Sun 15 NovAmsterdam Sloterdijk 20:58+2 min+4 min
Sat 14 NovAmsterdam Sloterdijk 20:540 min—
Fri 13 Nov— 20:53+6 min+6 min
Thu 12 Nov— 20:480 min—
Wed 11 Nov— 20:470 min—
Tue 10 Nov— 20:480 min—
Mon 9 Nov— 20:480 min—
Sat 7 NovAmsterdam Sloterdijk 20:54Partial coverage0 min—
Fri 6 Nov— 20:48+1 min+1 min
Thu 5 Nov— 20:48No data—
Wed 4 Nov— 20:480 min—
Tue 3 Nov— 20:48No data—
Mon 2 Nov— 20:480 min—
Sun 1 NovAmsterdam Sloterdijk 20:54Partial coverage0 min—
Sat 31 OctAmsterdam Sloterdijk 20:54Partial coverage0 min—
Fri 30 Oct— 20:47No data—
Wed 28 Oct— 20:56No data—
Tue 27 Oct— 20:48No data—
Mon 26 Oct— 20:48No data—
Sun 25 OctAmsterdam Sloterdijk 20:54No data—
Sat 24 OctAmsterdam Sloterdijk 20:55No data—
Fri 23 Oct— 20:480 min+1 min
Thu 22 Oct— 20:48No data—
Wed 21 Oct— 20:48No data—