Train NS 2121 Amsterdam Centraal – Den Haag Centraal

Amsterdam Centraal 08:20 → Den Haag Centraal 09:09 Mon, Tue, Wed, Thu, Fri, Sat 0 h 49 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Leiden Centraal at 09:13 0 min

  1. Amsterdam Centraal08:20
  2. Amsterdam Sloterdijk08:25
  3. Haarlem08:35
  4. Heemstede-Aerdenhout08:42
  5. Leiden Centraal08:56
  6. Den Haag Centraal09:09

Next service: tomorrow 08:20 from Amsterdam Centraal · Thu 19 Nov

Next departure 08:20 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 4 no data
On-time · 90 days
98%
63/64 runs under 3 min
RT coverage: 61 full · 3 partial · 13 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: +1 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

Worst days

  • Fri 9 Oct Max en route +6 min · last fix heading to Leiden Centraal +5 min

Distribution · 90 days

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

  • Early 25% · 16
  • On time 73% · 47
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=11
  • 100% T n=9
  • 100% W n=11
  • 100% T n=11
  • 90% F n=10
  • 100% S n=11
  • 100% S n=1

Stops and timetable

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

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