Train NS 8249 Amsterdam Centraal → Hoofddorp

Amsterdam Centraal 13:18 → Hoofddorp 13:42 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

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

It has not run yet today

Last recorded run: Saturday 21 November 0 min

Next service: today 13:18 from Amsterdam Centraal · Sun 22 Nov

Next departure 13:18 today · Amsterdam Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 2 full · 20 partial · 7 no data
On-time · 90 days
100%
33/33 runs under 3 min
RT coverage: 7 full · 26 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 33
  • 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=6
  • 100% W n=6
  • 100% T n=5
  • 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, 34 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
13:18on time on time
13:24 / 13:25≈ on time ≈ on time
13:29≈ on time ≈ on time
13:35 / 13:38≈ on time ≈ on time
13:42on time on time

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
Sat 21 NovSchiphol Airport 13:52Partial coverage0 min—
Fri 20 NovSchiphol Airport 13:52Partial coverage0 min—
Thu 19 NovSchiphol Airport 13:52Partial coverage0 min—
Wed 18 NovSchiphol Airport 13:52Partial coverage0 min—
Tue 17 NovSchiphol Airport 13:52Partial coverage0 min—
Mon 16 NovSchiphol Airport 13:53Partial coverage0 min—
Sun 15 NovSchiphol Airport 13:520 min—
Sat 14 NovSchiphol Airport 13:52+1 min+1 min
Fri 13 NovSchiphol Airport 13:52Partial coverage0 min—
Thu 12 NovSchiphol Airport 13:52Partial coverage0 min—
Wed 11 NovSchiphol Airport 13:52Partial coverage0 min—
Tue 10 NovSchiphol Airport 13:52Partial coverage0 min—
Mon 9 NovSchiphol Airport 13:52Partial coverage0 min—
Sun 8 NovSchiphol Airport 13:52Partial coverage0 min—
Sat 7 NovSchiphol Airport 13:52Partial coverage0 min—
Fri 6 NovSchiphol Airport 13:52No data—
Thu 5 NovSchiphol Airport 13:52No data—
Wed 4 NovSchiphol Airport 13:52Partial coverage0 min—
Tue 3 NovSchiphol Airport 13:52No data—
Mon 2 NovSchiphol Airport 13:54No data—
Sun 1 NovSchiphol Airport 13:53Partial coverage0 min—
Sat 31 OctSchiphol Airport 13:52Partial coverage0 min—
Fri 30 OctSchiphol Airport 13:52No data—
Thu 29 OctSchiphol Airport 13:52Partial coverage0 min—
Wed 28 OctSchiphol Airport 13:52Partial coverage0 min—
Tue 27 OctSchiphol Airport 13:52Partial coverage0 min—
Mon 26 OctSchiphol Airport 13:52No data—
Sun 25 OctSchiphol Airport 13:52No data—
Sat 24 OctSchiphol Airport 13:52Partial coverage0 min—
Fri 23 OctSchiphol Airport 13:52No data—