Train NS 4887 Amsterdam Centraal – Haarlem

Amsterdam Centraal 00:55 → Haarlem 01:14 Mon, Tue, Wed, Thu, Sun 0 h 19 min · 5 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to — at 01:14 0 min

  1. Amsterdam Centraal00:55
  2. Amsterdam Sloterdijk01:01
  3. Halfweg-Zwanenburg01:06
  4. Haarlem Spaarnwoude01:10
  5. Haarlem01:14

Next service: Sunday 00:55 from Amsterdam Centraal · Sun 22 Nov

Next departure 00:55 Sunday · Amsterdam Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 19 full · 0 partial · 0 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 5 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 Haarlem, 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

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

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

On-time by weekday

  • 100% M n=6
  • 100% T n=6
  • 100% W n=6
  • 100% T n=6
  • 100% F n=4
  • — S n=0
  • — S n=0

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
00:55on time on time
01:01≈ on time ≈ on time
01:06≈ on time ≈ on time
01:10≈ on time ≈ on time
01:14on 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
Thu 19 Nov— 01:140 min—
Wed 18 Nov— 01:140 min—
Tue 17 Nov— 01:140 min—
Mon 16 NovHaarlem Spaarnwoude 01:240 min—
Fri 13 Nov— 01:140 min—
Thu 12 Nov— 01:140 min—
Wed 11 Nov— 01:140 min—
Tue 10 Nov— 01:170 min—
Mon 9 NovHaarlem Spaarnwoude 01:280 min—
Fri 6 Nov— 01:140 min—
Thu 5 Nov— 01:180 min—
Mon 2 NovHaarlem Spaarnwoude 01:240 min—
Thu 29 Oct— 01:180 min—
Wed 28 Oct— 01:160 min—
Tue 27 Oct— 01:170 min—
Mon 26 OctHaarlem Spaarnwoude 01:260 min—
Fri 23 Oct— 01:200 min—
Thu 22 Oct— 01:160 min—
Wed 21 Oct— 01:150 min—
Tue 20 Oct— 01:240 min—
Mon 19 OctHaarlem Spaarnwoude 01:250 min—
Fri 16 Oct— 01:150 min—
Thu 15 Oct— 01:160 min—
Wed 14 Oct— 01:150 min—
Tue 13 Oct— 01:150 min—
Mon 12 OctHaarlem Spaarnwoude 01:250 min—
Wed 7 Oct— 01:170 min—
Tue 6 Oct— 01:200 min—
Mon 28 SeptHaarlem Spaarnwoude 01:26No data—
Mon 21 SeptHaarlem Spaarnwoude 01:24No data—