Train NS 2149 Amsterdam Centraal – Den Haag Centraal

Amsterdam Centraal 15:20 → Den Haag Centraal 16:13 Daily 0 h 53 min · 6 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Leiden Centraal at 16:17 +1 min

  1. Amsterdam Centraal15:20
  2. Amsterdam Sloterdijk15:25
  3. Haarlem15:35
  4. Heemstede-Aerdenhout15:42
  5. Leiden Centraal15:57
  6. Den Haag Centraal16:13

Next service: tomorrow 15:20 from Amsterdam Centraal · Sat 14 Nov

Next departure 15:20 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 15 full · 6 partial · 9 no data
On-time · 90 days
97%
64/66 runs under 3 min
RT coverage: 59 full · 7 partial · 23 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

  • Mon 7 Sept Max en route +10 min · last fix heading to Leiden Centraal +10 min
  • Wed 2 Sept Max en route +3 min · last fix heading to Amsterdam Centraal +3 min

Distribution · 90 days

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

  • Early 11% · 7
  • On time 86% · 57
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 66 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
15:20on time on time
15:25≈ on time ≈ on time
15:35 / 15:37≈ on time ≈ on time
15:42≈ on time ≈ on time
15:57 / 16:02≈ on time ≈ on time
16:13on 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 13 NovLeiden Centraal 16:17Partial coverage+1 min+2 min
Thu 12 NovLeiden Centraal 16:12+1 min—
Wed 11 NovLeiden Centraal 16:120 min—
Tue 10 NovLeiden Centraal 16:12+1 min+1 min
Mon 9 NovLeiden Centraal 16:120 min—
Sun 8 NovLeiden Centraal 16:17Partial coverage0 min—
Sat 7 NovLeiden Centraal 16:14Partial coverage0 min+1 min
Fri 6 NovLeiden Centraal 16:17No data—
Thu 5 NovLeiden Centraal 16:12No data—
Wed 4 NovLeiden Centraal 16:12+1 min+1 min
Tue 3 NovLeiden Centraal 16:12No data—
Mon 2 NovLeiden Centraal 16:120 min—
Sun 1 NovLeiden Centraal 16:17Partial coverage0 min—
Sat 31 OctLeiden Centraal 16:17Partial coverage+1 min—
Fri 30 OctLeiden Centraal 16:160 min—
Thu 29 OctLeiden Centraal 16:120 min—
Wed 28 OctLeiden Centraal 16:12No data—
Tue 27 OctLeiden Centraal 16:210 min—
Mon 26 OctLeiden Centraal 16:120 min—
Sun 25 OctLeiden Centraal 16:17No data—
Sat 24 OctLeiden Centraal 16:17+1 min+1 min
Fri 23 OctLeiden Centraal 16:17No data—
Thu 22 OctLeiden Centraal 16:120 min—
Wed 21 OctLeiden Centraal 16:12No data—
Tue 20 OctLeiden Centraal 16:130 min—
Mon 19 OctLeiden Centraal 16:130 min—
Sun 18 OctLeiden Centraal 16:17Partial coverage+1 min—
Sat 17 OctLeiden Centraal 16:16No data—
Fri 16 OctLeiden Centraal 16:16No data—
Thu 15 OctLeiden Centraal 16:130 min—