Train NS 28564 Haarlem – Amsterdam Centraal

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

Running now · updated 20:57

Heading to Amsterdam Centraal +3 min

Estimated arrival at Amsterdam Centraal 20:58 20:55 · 11 km/h

  1. Haarlem20:40
  2. Amsterdam Sloterdijk20:49
  3. Amsterdam Centraal20:55

Today it is running worse than usual: typical arrival delay is +1 min; 100% of the last 7 runs arrived on time.

On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 5 full · 2 partial · 3 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 6 full · 2 partial · 14 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 Amsterdam Centraal, 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

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

  • Early 0% · 0
  • On time 100% · 8
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • — W n=0
  • — T n=0
  • 100% F n=2
  • 100% 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, 8 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
20:40on time on time
20:49≈ on time ≈ on time
20:55on time +1 min

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:54Partial coverage+3 min+3 min
Sat 14 NovAmsterdam Sloterdijk 21:04Partial coverage+1 min—
Sun 8 NovDordrecht 19:38+1 min+2 min
Sat 7 NovDordrecht 19:37+1 min—
Sun 25 OctHilversum 19:05No data—
Sat 24 OctHilversum 19:050 min—
Fri 23 OctHilversum 19:000 min—
Thu 22 OctHilversum 19:06No data—
Wed 21 OctHilversum 19:01No data—
Tue 20 OctArnhem Centraal 19:010 min—
Fri 16 OctSchagen 20:160 min—
Sun 4 OctAmersfoort Centraal 18:46No data—
Sun 27 SeptAmersfoort Centraal 19:48No data—
Sat 26 SeptAmersfoort Centraal 19:47No data—
Sun 20 SeptGeldermalsen 20:08No data—
Sat 19 SeptGeldermalsen 20:09No data—
Sun 13 SeptRotterdam Alexander 19:46No data—
Sat 12 SeptRotterdam Alexander 19:47No data—
Sun 30 AugAmersfoort Centraal 19:47No data—
Sat 29 AugAmersfoort Centraal 19:49No data—
Sun 23 AugAmsterdam Zuid 19:30No data—
Sat 22 AugAmsterdam Zuid 19:30No data—