Train NS 2142 Haarlem – Amsterdam Centraal

Haarlem 14:55 → Amsterdam Centraal 15:10 Daily 0 h 15 min · 3 stops NS (Nederlandse Spoorwegen)

Running now · updated 14:09

Position estimated from the timetable

Heading to Amsterdam Centraal 0 min

Estimated arrival at Amsterdam Centraal 15:10

  1. Haarlem14:55
  2. Amsterdam Sloterdijk15:04
  3. Amsterdam Centraal15:10

Today it is running no worse than usual: typical arrival delay is 0 min; 91% of the last 22 runs arrived on time.

On-time · 30 days
91%
20/22 runs under 3 min
RT coverage: 20 full · 2 partial · 7 no data
On-time · 90 days
94%
32/34 runs under 3 min
RT coverage: 32 full · 2 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 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 14 Nov Max en route +9 min · last fix heading to Amsterdam Sloterdijk +7 min
  • Sat 24 Oct Max en route +4 min · last fix heading to Amsterdam Sloterdijk +4 min

Distribution · 90 days

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

  • Early 3% · 1
  • On time 91% · 31
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=4
  • 100% W n=5
  • 100% T n=5
  • 100% F n=3
  • 60% S n=5
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (3 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 10Today
14:55on time on time
15:04≈ on time ≈ +1 min
15:10on 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 15:19Partial coverage+1 min+1 min
Sat 14 NovAmsterdam Sloterdijk 15:27Partial coverage+7 min+9 min
Fri 13 NovAmsterdam Sloterdijk 15:190 min+1 min
Thu 12 NovAmsterdam Sloterdijk 15:23+2 min+2 min
Wed 11 NovAmsterdam Sloterdijk 15:190 min—
Tue 10 NovAmsterdam Sloterdijk 15:19+1 min—
Mon 9 NovAmsterdam Sloterdijk 15:19+1 min+2 min
Sun 8 NovAmsterdam Sloterdijk 15:19+1 min—
Sat 7 NovAmsterdam Sloterdijk 15:190 min—
Fri 6 NovAmsterdam Sloterdijk 15:27No data—
Thu 5 NovAmsterdam Sloterdijk 15:19No data—
Wed 4 NovAmsterdam Sloterdijk 15:190 min+1 min
Tue 3 NovAmsterdam Sloterdijk 15:20No data—
Mon 2 NovAmsterdam Sloterdijk 15:190 min—
Sun 1 NovAmsterdam Sloterdijk 15:200 min—
Sat 31 OctAmsterdam Sloterdijk 15:190 min+1 min
Fri 30 OctAmsterdam Sloterdijk 15:210 min—
Thu 29 OctAmsterdam Sloterdijk 15:190 min—
Wed 28 OctAmsterdam Sloterdijk 15:20No data—
Tue 27 OctAmsterdam Sloterdijk 15:190 min—
Mon 26 OctAmsterdam Sloterdijk 15:190 min—
Sun 25 OctAmsterdam Sloterdijk 15:19No data—
Sat 24 OctAmsterdam Sloterdijk 15:20+4 min+4 min
Fri 23 OctAmsterdam Sloterdijk 15:20No data—
Thu 22 OctAmsterdam Sloterdijk 15:230 min—
Wed 21 OctAmsterdam Sloterdijk 15:23No data—
Tue 20 OctAmsterdam Sloterdijk 15:200 min—
Mon 19 OctAmsterdam Sloterdijk 15:200 min—
Sun 18 OctAmsterdam Sloterdijk 15:20+1 min+2 min
Sat 17 OctAmsterdam Sloterdijk 15:19No data—