Train NS 8285 Amsterdam Centraal → Hoofddorp

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

NS 8285 Amsterdam Centraal–Hoofddorp: final delay under 3 min on 19 of its 21 runs with data in the last 30 days (90%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:33 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 22:18 from Amsterdam Centraal · Sun 22 Nov

Next departure 22:18 today · Amsterdam Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 17 full · 4 partial · 7 no data
On-time · 90 days
94%
31/33 runs under 3 min
RT coverage: 28 full · 5 partial · 21 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: +3 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

  • Thu 19 Nov Max en route +10 min · last fix heading to — +9 min
  • Sun 8 Nov Max en route +3 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 80% T n=5
  • 100% F n=6
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

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