Train NS 8255 Amsterdam Centraal → Hoofddorp

Amsterdam Centraal 14:48 → Hoofddorp 15:12 Daily 0 h 24 min · 5 stops NS (Nederlandse Spoorwegen)

NS 8255 Amsterdam Centraal–Hoofddorp: final delay under 3 min on 17 of its 19 runs with data in the last 30 days (89%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 12:46 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November +2 min

Next service: today 14:48 from Amsterdam Centraal · Sun 22 Nov

Next departure 14:48 today · Amsterdam Centraal
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 1 full · 18 partial · 10 no data
On-time · 90 days
93%
26/28 runs under 3 min
RT coverage: 3 full · 25 partial · 54 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

  • Fri 13 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min
  • Thu 12 Nov Max en route +4 min · last fix heading to Schiphol Airport +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 26
  • 3–10 min 7% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
14:48on time on time
14:54 / 14:55— —
14:59— —
15:05 / 15:08— —
15:12— —

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