Train NS 28562 Haarlem – Amsterdam Centraal

Haarlem 20:10 → Amsterdam Centraal 20:25 Sat, Sun 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Amsterdam Sloterdijk at 20:34 +1 min

  1. Haarlem20:10
  2. Amsterdam Sloterdijk20:19
  3. Amsterdam Centraal20:25
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 3 full · 2 partial · 5 no data
On-time · 90 days
83%
5/6 runs under 3 min
RT coverage: 4 full · 2 partial · 28 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: +3 min

Last 30 days

Arrival delay at Amsterdam Centraal, 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 24 Oct Max en route +5 min · last fix heading to Hilversum +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 83% · 5
  • 3–10 min 17% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • 100% F n=1
  • 67% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 6 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
20:10on time on time
20:19— —
20:25— —

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 15 NovAmsterdam Sloterdijk 20:34Partial coverage+1 min+1 min
Sat 14 NovAmsterdam Sloterdijk 20:33Partial coverage0 min—
Sun 8 NovDordrecht 19:07+1 min—
Sat 7 NovDordrecht 19:040 min—
Sun 25 OctHilversum 18:35No data—
Sat 24 OctHilversum 18:50+4 min+5 min
Fri 23 OctHilversum 18:31No data—
Thu 22 OctHilversum 18:30No data—
Wed 21 OctHilversum 18:31No data—
Tue 20 OctHilversum 18:23No data—
Fri 16 OctDen Helder Zuid 19:510 min—
Sun 4 OctAmersfoort Centraal 18:21No data—
Sun 27 SeptAmersfoort Centraal 19:18No data—
Sat 26 SeptAmersfoort Centraal 19:17No data—
Sun 20 SeptGeldermalsen 19:38No data—
Sat 19 SeptGeldermalsen 19:38No data—
Sun 13 SeptRotterdam Alexander 19:17No data—
Sat 12 SeptRotterdam Alexander 19:16No data—
Fri 11 SeptRoosendaal 18:38No data—
Thu 10 SeptRilland-Bath 18:16No data—
Tue 8 SeptRilland-Bath 18:16No data—
Mon 7 SeptRoosendaal 18:38No data—
Fri 4 SeptRoosendaal 18:37No data—
Thu 3 SeptRilland-Bath 18:15No data—
Wed 2 SeptBergen op Zoom 18:25No data—
Tue 1 SeptKrabbendijke 18:12No data—
Mon 31 AugBergen op Zoom 18:25No data—
Sun 30 AugAmersfoort Centraal 19:18No data—
Sat 29 AugAmersfoort Centraal 19:16No data—
Thu 27 AugSchiphol Airport 19:00No data—