Train NS 8173 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

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

Next departure 19:35 today · Amsterdam Centraal
On-time · 30 days
100%
12/12 runs under 3 min
RT coverage: 8 full · 4 partial · 15 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 11 full · 4 partial · 22 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

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

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

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=3
  • 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, 15 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
19:35on time on time
19:40≈ on time ≈ on time
19:44≈ on time ≈ on time
19:50 / 19:53≈ on time ≈ on time
19:57on time on time

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 Nov— 19:580 min—
Thu 5 Nov— 19:59No data—
Wed 4 Nov— 19:590 min—
Tue 3 Nov— 19:58No data—
Mon 2 Nov— 19:59No data—
Sun 1 NovSchiphol Airport 20:07Partial coverage+1 min+1 min
Sat 31 OctSchiphol Airport 20:07Partial coverage+2 min+2 min
Fri 30 Oct— 20:02No data—
Thu 29 Oct— 19:580 min—
Wed 28 Oct— 20:080 min—
Tue 27 Oct— 20:00No data—
Mon 26 OctSchiphol Airport 19:58No data—
Sun 25 OctSchiphol Airport 20:07No data—
Sat 24 OctSchiphol Airport 20:07No data—
Fri 23 Oct— 19:580 min—
Thu 22 Oct— 20:00No data—
Wed 21 Oct— 19:59No data—
Tue 20 Oct— 20:040 min—
Mon 19 Oct— 19:59No data—
Sun 18 OctSchiphol Airport 20:07Partial coverage0 min—
Sat 17 OctSchiphol Airport 20:07Partial coverage0 min—
Fri 16 OctSchiphol Airport 20:07No data—
Thu 15 Oct— 19:59No data—
Wed 14 OctAmsterdam Lelylaan 19:59No data—
Tue 13 Oct— 19:59No data—
Mon 12 Oct— 19:580 min—
Fri 9 Oct— 19:590 min+1 min
Thu 8 Oct— 20:070 min—
Wed 7 Oct— 19:580 min—
Tue 6 Oct— 19:580 min—