Train NS 2141 Amsterdam Centraal – Den Haag Centraal

Amsterdam Centraal 13:20 → Den Haag Centraal 14:09 Daily 0 h 49 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Leiden Centraal at 14:14 No data

  1. Amsterdam Centraal13:20
  2. Amsterdam Sloterdijk13:25
  3. Haarlem13:35
  4. Heemstede-Aerdenhout13:41
  5. Leiden Centraal13:56
  6. Den Haag Centraal14:09

Next service: tomorrow 13:20 from Amsterdam Centraal · Sat 7 Nov

Next departure 13:20 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 11 full · 10 partial · 9 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 12 full · 12 partial · 65 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: 0 min

Last 30 days

Arrival delay at Den Haag 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
13:20on time on time
13:25≈ on time ≈ on time
13:35 / 13:36≈ on time ≈ on time
13:41≈ on time ≈ on time
13:56 / 13:58≈ on time ≈ +1 min
14:09on 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
Fri 6 NovLeiden Centraal 14:14No data—
Thu 5 NovLeiden Centraal 14:12No data—
Wed 4 NovLeiden Centraal 14:12Partial coverage0 min—
Tue 3 NovLeiden Centraal 14:12No data—
Mon 2 NovLeiden Centraal 14:12Partial coverage0 min—
Sun 1 NovLeiden Centraal 14:170 min—
Sat 31 OctLeiden Centraal 14:160 min—
Fri 30 OctLeiden Centraal 14:170 min—
Thu 29 OctLeiden Centraal 14:13Partial coverage0 min—
Wed 28 OctLeiden Centraal 14:12No data—
Tue 27 OctLeiden Centraal 14:12Partial coverage0 min—
Mon 26 OctLeiden Centraal 14:13Partial coverage0 min—
Sun 25 OctLeiden Centraal 14:17No data—
Sat 24 OctLeiden Centraal 14:170 min+1 min
Fri 23 OctLeiden Centraal 14:170 min—
Thu 22 OctLeiden Centraal 14:12Partial coverage0 min—
Wed 21 OctLeiden Centraal 14:18No data—
Tue 20 OctLeiden Centraal 14:13Partial coverage0 min—
Mon 19 OctLeiden Centraal 14:12Partial coverage0 min—
Sun 18 OctLeiden Centraal 14:170 min—
Sat 17 OctLeiden Centraal 14:170 min—
Fri 16 OctLeiden Centraal 14:160 min—
Thu 15 OctLeiden Centraal 14:19No data—
Wed 14 OctLeiden Centraal 14:13Partial coverage0 min—
Tue 13 OctLeiden Centraal 14:12No data—
Mon 12 OctLeiden Centraal 14:12No data—
Sun 11 OctAmsterdam Sloterdijk 13:40+1 min—
Sat 10 OctAmsterdam Sloterdijk 13:400 min—
Fri 9 OctLeiden Centraal 14:170 min—
Thu 8 OctLeiden Centraal 14:13Partial coverage+2 min+3 min