Train NS 8357 Amsterdam Centraal – Hoofddorp

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

It has not run yet today

Last recorded run: Monday 16 November 0 min

Next service: today 15:43 from Amsterdam Centraal · Tue 17 Nov

Next departure 15:43 today · Amsterdam Centraal
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 2 full · 13 partial · 14 no data
On-time · 90 days
91%
20/22 runs under 3 min
RT coverage: 4 full · 18 partial · 55 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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 10 Oct Max en route +8 min · last fix heading to Schiphol Airport +8 min
  • Sun 15 Nov Max en route +4 min · last fix heading to Schiphol Airport +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 20
  • 3–10 min 9% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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