Train NS 8363 Amsterdam Centraal – Hoofddorp

Amsterdam Centraal 17:13 → Hoofddorp 17:34 Daily 0 h 21 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

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

  1. Amsterdam Centraal17:13
  2. Amsterdam Sloterdijk17:19
  3. Amsterdam Lelylaan17:23
  4. Schiphol Airport17:29
  5. Hoofddorp17:34

Next service: tomorrow 17:13 from Amsterdam Centraal · Mon 9 Nov

Next departure 17:13 tomorrow · Amsterdam Centraal
On-time · 30 days
87%
13/15 runs under 3 min
RT coverage: 10 full · 5 partial · 13 no data
On-time · 90 days
83%
15/18 runs under 3 min
RT coverage: 13 full · 5 partial · 60 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
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

  • Sat 10 Oct Max en route +8 min · last fix heading to Schiphol Airport +8 min
  • Tue 6 Oct Max en route +5 min · last fix heading to Schiphol Airport +5 min
  • Sun 11 Oct Max en route +4 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=1
  • 50% T n=2
  • 100% W n=3
  • 100% T n=3
  • 100% F n=2
  • 75% 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, 18 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:13on time on time
17:19≈ on time ≈ +1 min
17:23≈ on time ≈ +2 min
17:29 / 17:30≈ on time ≈ +3 min
17:34on time +5 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
Sun 8 NovSchiphol Airport 17:44Partial coverage0 min—
Sat 7 NovSchiphol Airport 17:44Partial coverage0 min—
Fri 6 NovSchiphol Airport 17:44+1 min+1 min
Thu 5 NovSchiphol Airport 17:44No data—
Wed 4 NovSchiphol Airport 17:44No data—
Tue 3 NovSchiphol Airport 17:44No data—
Mon 2 NovSchiphol Airport 17:39No data—
Sun 1 NovSchiphol Airport 17:45Partial coverage0 min—
Sat 31 OctSchiphol Airport 17:44Partial coverage0 min—
Fri 30 OctSchiphol Airport 17:51No data—
Thu 29 OctSchiphol Airport 17:440 min—
Wed 28 OctSchiphol Airport 17:440 min—
Tue 27 OctSchiphol Airport 17:55No data—
Mon 26 OctSchiphol Airport 17:44No data—
Sun 25 OctSchiphol Airport 17:47No data—
Sat 24 OctSchiphol Airport 17:47Partial coverage+3 min+3 min
Fri 23 OctSchiphol Airport 17:46No data—
Thu 22 OctSchiphol Airport 17:440 min—
Wed 21 OctSchiphol Airport 17:440 min—
Tue 20 OctSchiphol Airport 17:440 min—
Mon 19 OctSchiphol Airport 17:44No data—
Fri 16 OctSchiphol Airport 17:44No data—
Thu 15 OctSchiphol Airport 17:55No data—
Wed 14 OctSchiphol Airport 17:450 min—
Tue 13 OctSchiphol Airport 17:44No data—
Mon 12 OctSchiphol Airport 17:450 min—
Sun 11 OctSchiphol Airport 17:49+3 min+4 min
Sat 10 OctSchiphol Airport 17:50+8 min+8 min
Fri 9 OctSchiphol Airport 17:440 min—
Thu 8 OctSchiphol Airport 17:450 min—