Train NS 8337 Amsterdam Centraal – Hoofddorp

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

✓ Today’s run finished

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

  1. Amsterdam Centraal10:43
  2. Amsterdam Sloterdijk10:48
  3. Amsterdam Lelylaan10:52
  4. Schiphol Airport10:58
  5. Hoofddorp11:04

Next service: tomorrow 10:43 from Amsterdam Centraal · Sat 21 Nov

Next departure 10:43 tomorrow · Amsterdam Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 2 full · 17 partial · 11 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 6 full · 24 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Sun 15 Nov Max en route +6 min · last fix heading to Schiphol Airport +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 29
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
10:43on time on time
10:48≈ on time ≈ +1 min
10:52≈ on time ≈ +1 min
10:58 / 11:00≈ on time ≈ +2 min
11:04on time +3 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
Fri 20 NovSchiphol Airport 11:14Partial coverage0 min+1 min
Thu 19 NovSchiphol Airport 11:14Partial coverage0 min—
Wed 18 NovSchiphol Airport 11:14Partial coverage0 min+1 min
Tue 17 NovSchiphol Airport 11:14Partial coverage0 min+1 min
Mon 16 NovSchiphol Airport 11:14Partial coverageNo data—
Sun 15 NovSchiphol Airport 11:19+6 min+6 min
Sat 14 NovSchiphol Airport 11:140 min—
Fri 13 NovSchiphol Airport 11:14Partial coverage+2 min+3 min
Thu 12 NovSchiphol Airport 11:14Partial coverage+1 min—
Wed 11 NovSchiphol Airport 11:14Partial coverage0 min—
Tue 10 NovSchiphol Airport 11:14Partial coverage0 min+2 min
Mon 9 NovSchiphol Airport 11:14Partial coverage0 min—
Sun 8 NovSchiphol Airport 11:14Partial coverage0 min—
Sat 7 NovSchiphol Airport 11:17Partial coverage+2 min+4 min
Fri 6 NovSchiphol Airport 11:14No data—
Thu 5 NovSchiphol Airport 11:14No data—
Wed 4 NovSchiphol Airport 11:14Partial coverage0 min—
Tue 3 NovSchiphol Airport 11:14No data—
Mon 2 NovSchiphol Airport 11:14Partial coverage0 min—
Sun 1 NovSchiphol Airport 11:18Partial coverage+3 min+4 min
Sat 31 OctSchiphol Airport 11:14Partial coverage0 min—
Fri 30 OctSchiphol Airport 11:14No data—
Thu 29 OctSchiphol Airport 11:14No data—
Wed 28 OctSchiphol Airport 11:16No data—
Tue 27 OctSchiphol Airport 11:14No data—
Mon 26 OctSchiphol Airport 11:15Partial coverage0 min—
Sun 25 OctSchiphol Airport 11:14No data—
Sat 24 OctSchiphol Airport 11:14Partial coverage0 min—
Fri 23 OctSchiphol Airport 11:15No data—
Thu 22 OctSchiphol Airport 11:14No data—