Train NS 8250 Hoofddorp – Amsterdam Centraal

Hoofddorp 15:47 → Amsterdam Centraal 16:10 Daily 0 h 23 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 16:18 No data

  1. Hoofddorp15:47
  2. Schiphol Airport15:51
  3. Amsterdam Lelylaan15:59
  4. Amsterdam Sloterdijk16:02
  5. Amsterdam Centraal16:10

Next service: tomorrow 15:47 from Hoofddorp · Fri 6 Nov

Next departure 15:47 tomorrow · Hoofddorp
On-time · 30 days
94%
15/16 runs under 3 min
RT coverage: 7 full · 9 partial · 14 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 14 full · 10 partial · 47 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: +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

  • Sun 18 Oct Max en route +3 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
15:47on time on time
15:51 / 15:53≈ on time ≈ +2 min
15:59≈ on time ≈ +2 min
16:02 / 16:04≈ on time ≈ +2 min
16:10on 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
Thu 5 NovAmsterdam Sloterdijk 16:18No data—
Wed 4 NovAmsterdam Sloterdijk 16:18Partial coverage0 min—
Tue 3 NovAmsterdam Sloterdijk 16:19No data—
Mon 2 NovAmsterdam Sloterdijk 16:24No data—
Sun 1 NovAmsterdam Sloterdijk 16:190 min—
Sat 31 OctAmsterdam Sloterdijk 16:20+2 min+4 min
Fri 30 OctAmsterdam Sloterdijk 16:18No data—
Thu 29 OctAmsterdam Sloterdijk 16:18Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 16:19Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 16:18Partial coverage0 min—
Mon 26 OctAmsterdam Sloterdijk 16:18No data—
Sun 25 OctAmsterdam Sloterdijk 16:18No data—
Sat 24 OctAmsterdam Sloterdijk 16:170 min—
Fri 23 OctAmsterdam Sloterdijk 16:19No data—
Thu 22 OctAmsterdam Sloterdijk 16:22Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 16:18No data—
Tue 20 OctAmsterdam Sloterdijk 16:19Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 16:19No data—
Sun 18 OctAmsterdam Sloterdijk 16:19+3 min+3 min
Sat 17 OctAmsterdam Sloterdijk 16:28No data—
Fri 16 OctAmsterdam Sloterdijk 16:180 min—
Thu 15 OctAmsterdam Sloterdijk 16:18No data—
Wed 14 OctAmsterdam Sloterdijk 16:18No data—
Tue 13 OctAmsterdam Sloterdijk 16:18No data—
Mon 12 OctAmsterdam Sloterdijk 16:18Partial coverage0 min—
Sun 11 OctAmsterdam Sloterdijk 16:18+1 min+1 min
Sat 10 OctAmsterdam Sloterdijk 16:17No data—
Fri 9 OctAmsterdam Sloterdijk 16:19+2 min+2 min
Thu 8 OctAmsterdam Sloterdijk 16:18Partial coverage0 min—
Wed 7 OctAmsterdam Sloterdijk 16:18Partial coverage+1 min+1 min