Train NS 8345 Amsterdam Centraal – Hoofddorp

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

Running now · updated 00:48

Heading to Hoofddorp 0 min

Estimated arrival at Hoofddorp 13:04 · 6 km/h

  1. Amsterdam Centraal12:43
  2. Amsterdam Sloterdijk12:48
  3. Amsterdam Lelylaan12:52
  4. Schiphol Airport12:58
  5. Hoofddorp13:04

Today it is running no worse than usual: typical arrival delay is 0 min; 94% of the last 17 runs arrived on time.

On-time · 30 days
94%
16/17 runs under 3 min
RT coverage: 2 full · 15 partial · 9 no data
On-time · 90 days
96%
24/25 runs under 3 min
RT coverage: 4 full · 21 partial · 52 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: +2 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 7 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 24
  • 3–10 min 4% · 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=3
  • 100% T n=2
  • 100% F n=2
  • 80% S n=5
  • 100% S n=4

Stops and timetable

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

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