Train NS 2145 Amsterdam Centraal – Den Haag Centraal

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

✓ Today’s run finished

Today, last fix heading to Leiden Centraal at 15:17 0 min

  1. Amsterdam Centraal14:20
  2. Amsterdam Sloterdijk14:25
  3. Haarlem14:35
  4. Heemstede-Aerdenhout14:42
  5. Leiden Centraal14:57
  6. Den Haag Centraal15:13

Next service: tomorrow 14:20 from Amsterdam Centraal · Sun 8 Nov

Next departure 14:20 tomorrow · Amsterdam Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 9 full · 7 partial · 14 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 45 full · 7 partial · 37 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

Worst days

  • Fri 4 Sept Max en route +44 min · last fix heading to Amsterdam Centraal +43 min
  • Wed 7 Oct Max en route +7 min · last fix heading to Leiden Centraal +5 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=5
  • 86% W n=7
  • 100% T n=8
  • 89% F n=9
  • 100% S n=9
  • 100% S n=7

Stops and timetable

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

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