Train NS 8273 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

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

Next departure 19:18 today · Amsterdam Centraal
On-time · 30 days
93%
13/14 runs under 3 min
RT coverage: 9 full · 5 partial · 14 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 12 full · 5 partial · 25 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: 0 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

Worst days

  • Sun 1 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 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=3
  • 100% F n=3
  • 100% S n=2
  • 67% S n=3

Stops and timetable

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

Last 90 days, 17 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:18on time on time
19:24 / 19:25≈ on time ≈ on time
19:29≈ on time ≈ on time
19:35 / 19:38≈ on time ≈ on time
19:42on 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:430 min—
Thu 5 Nov— 19:44No data—
Wed 4 Nov— 19:440 min—
Tue 3 Nov— 19:43No data—
Mon 2 Nov— 19:49No data—
Sun 1 NovSchiphol Airport 19:53Partial coverage+4 min+4 min
Sat 31 OctSchiphol Airport 19:52Partial coverage0 min—
Fri 30 Oct— 19:43No data—
Thu 29 Oct— 19:440 min—
Tue 27 Oct— 19:45No data—
Mon 26 Oct— 19:430 min—
Sun 25 OctSchiphol Airport 19:52No data—
Sat 24 OctSchiphol Airport 19:52Partial coverage0 min—
Fri 23 OctAmsterdam Sloterdijk 19:43Partial coverage0 min—
Thu 22 Oct— 19:440 min—
Wed 21 Oct— 19:44No data—
Tue 20 Oct— 19:440 min—
Mon 19 Oct— 19:44No data—
Sun 18 OctSchiphol Airport 19:52Partial coverage0 min—
Sat 17 OctSchiphol Airport 19:52No data—
Fri 16 OctSchiphol Airport 19:52No data—
Thu 15 Oct— 19:43No data—
Wed 14 OctSchiphol Airport 19:52No data—
Tue 13 Oct— 19:43No data—
Mon 12 Oct— 19:440 min—
Sun 11 OctSchiphol Airport 19:520 min—
Sat 10 Oct— 19:44No data—
Fri 9 Oct— 19:430 min—
Thu 8 Oct— 19:430 min—
Wed 7 Oct— 19:43+1 min+1 min