Train NS 8256 Hoofddorp – Amsterdam Centraal

Hoofddorp 17:17 → Amsterdam Centraal 17:39 Daily 0 h 22 min · 5 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 17:17 from Hoofddorp · Thu 5 Nov

Next departure 17:17 today · Hoofddorp
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 1 full · 10 partial · 18 no data
On-time · 90 days
83%
10/12 runs under 3 min
RT coverage: 1 full · 11 partial · 58 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sat 24 Oct Max en route +8 min · last fix heading to Amsterdam Sloterdijk +7 min
  • Wed 7 Oct Max en route +5 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 10
  • 3–10 min 17% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=2
  • 0% W n=1
  • 100% T n=1
  • 100% F n=2
  • 50% S n=2
  • 100% S n=3

Stops and timetable

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

Last 90 days, 12 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
17:17on time +1 min
17:21 / 17:22— —
17:29— —
17:33— —
17:39— —

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
Wed 4 NovAmsterdam Sloterdijk 17:47No data—
Tue 3 NovAmsterdam Sloterdijk 17:47No data—
Mon 2 NovAmsterdam Sloterdijk 17:47No data—
Sun 1 NovAmsterdam Sloterdijk 17:47Partial coverage+1 min+1 min
Sat 31 OctAmsterdam Sloterdijk 17:48Partial coverage0 min—
Fri 30 OctAmsterdam Sloterdijk 17:47No data—
Thu 29 OctAmsterdam Sloterdijk 17:47No data—
Wed 28 OctAmsterdam Sloterdijk 17:47No data—
Tue 27 OctAmsterdam Sloterdijk 17:47No data—
Mon 26 OctAmsterdam Sloterdijk 17:47No data—
Sun 25 OctAmsterdam Sloterdijk 17:47No data—
Sat 24 OctAmsterdam Sloterdijk 17:55Partial coverage+7 min+8 min
Fri 23 OctAmsterdam Sloterdijk 17:47Partial coverage0 min—
Thu 22 OctAmsterdam Sloterdijk 17:44No data—
Wed 21 OctAmsterdam Sloterdijk 17:47No data—
Tue 20 OctAmsterdam Sloterdijk 17:47Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 17:47No data—
Sun 18 OctAmsterdam Sloterdijk 17:48Partial coverage0 min—
Sat 17 OctAmsterdam Sloterdijk 17:51No data—
Fri 16 OctAmsterdam Sloterdijk 17:49No data—
Thu 15 OctAmsterdam Sloterdijk 17:48No data—
Wed 14 OctAmsterdam Sloterdijk 17:47No data—
Tue 13 OctAmsterdam Sloterdijk 17:47No data—
Mon 12 OctAmsterdam Sloterdijk 17:47Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 17:48+1 min—
Sat 10 OctAmsterdam Sloterdijk 17:47No data—
Fri 9 OctAmsterdam Sloterdijk 17:47Partial coverage+2 min+3 min
Thu 8 OctAmsterdam Sloterdijk 17:47Partial coverage0 min—
Wed 7 OctAmsterdam Sloterdijk 17:49Partial coverage+3 min+5 min
Tue 6 OctAmsterdam Sloterdijk 17:47Partial coverage+2 min+3 min