Train NS 8361 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 16:43 → Hoofddorp 17:04 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Schiphol Airport at 17:14 0 min

  1. Amsterdam Centraal16:43
  2. Amsterdam Sloterdijk16:48
  3. Amsterdam Lelylaan16:52
  4. Schiphol Airport16:58
  5. Hoofddorp17:04

Next service: tomorrow 16:43 from Amsterdam Centraal · Sun 8 Nov

Next departure 16:43 tomorrow · Amsterdam Centraal
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 2 full · 9 partial · 17 no data
On-time · 90 days
79%
11/14 runs under 3 min
RT coverage: 2 full · 12 partial · 64 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+8min
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

  • Wed 7 Oct Max en route +10 min · last fix heading to Schiphol Airport +10 min
  • Sat 10 Oct Max en route +10 min · last fix heading to Amsterdam Centraal +10 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 79% · 11
  • 3–10 min 14% · 2
  • 10–30 min 7% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
16:43on time on time
16:48— —
16:52— —
16:58 / 17:00— —
17:04— —

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 7 NovSchiphol Airport 17:14Partial coverage0 min—
Fri 6 NovSchiphol Airport 17:14Partial coverage0 min—
Thu 5 NovSchiphol Airport 17:14No data—
Wed 4 NovSchiphol Airport 17:14No data—
Tue 3 NovSchiphol Airport 17:14No data—
Mon 2 NovSchiphol Airport 17:14No data—
Sun 1 NovSchiphol Airport 17:17Partial coverage+3 min+4 min
Sat 31 OctSchiphol Airport 17:14Partial coverage0 min—
Fri 30 OctSchiphol Airport 17:14No data—
Thu 29 OctSchiphol Airport 17:14No data—
Wed 28 OctSchiphol Airport 17:14No data—
Tue 27 OctSchiphol Airport 17:14No data—
Mon 26 OctSchiphol Airport 17:14Partial coverage0 min—
Sun 25 OctSchiphol Airport 17:15No data—
Sat 24 OctSchiphol Airport 17:14Partial coverage0 min—
Fri 23 OctSchiphol Airport 17:15No data—
Thu 22 OctSchiphol Airport 17:16No data—
Wed 21 OctSchiphol Airport 17:16No data—
Tue 20 OctSchiphol Airport 17:16Partial coverage0 min—
Mon 19 OctSchiphol Airport 17:14No data—
Fri 16 OctSchiphol Airport 17:14No data—
Thu 15 OctSchiphol Airport 17:14No data—
Wed 14 OctSchiphol Airport 17:14No data—
Tue 13 OctSchiphol Airport 17:15No data—
Mon 12 OctSchiphol Airport 17:14Partial coverage0 min—
Sun 11 OctSchiphol Airport 17:140 min—
Sat 10 OctAmsterdam Centraal 17:32+10 min+10 min
Fri 9 OctSchiphol Airport 17:17Partial coverage+3 min+4 min
Thu 8 OctSchiphol Airport 17:14Partial coverage0 min—
Wed 7 OctSchiphol Airport 17:21Partial coverage+10 min+10 min