Train NS 8339 Amsterdam Centraal → Hoofddorp

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

NS 8339 Amsterdam Centraal–Hoofddorp: final delay under 3 min on 23 of its 23 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 23:44 (GMT+1).

✓ Today’s run finished

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

  1. Amsterdam Centraal11:13
  2. Amsterdam Sloterdijk11:19
  3. Amsterdam Lelylaan11:23
  4. Schiphol Airport11:29
  5. Hoofddorp11:34

Next service: tomorrow 11:13 from Amsterdam Centraal · Mon 23 Nov

Next departure 11:13 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 2 full · 21 partial · 7 no data
On-time · 90 days
100%
31/31 runs under 3 min
RT coverage: 4 full · 27 partial · 49 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: +1 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 31
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 31 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
11:13on time on time
11:19— —
11:23— —
11:29 / 11:30— —
11:34— —

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