Train NS 2140 Den Haag Centraal – Amsterdam Centraal

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

It has not run yet today

Last recorded run: Tuesday 17 November 0 min

Next service: today 13:51 from Den Haag Centraal · Wed 18 Nov

Next departure 13:51 today · Den Haag Centraal
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 10 full · 11 partial · 8 no data
On-time · 90 days
97%
62/64 runs under 3 min
RT coverage: 48 full · 16 partial · 24 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Sun 8 Nov Max en route +5 min · last fix heading to Amsterdam Sloterdijk +4 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Amsterdam Sloterdijk +3 min

Distribution · 90 days

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

  • Early 3% · 2
  • On time 94% · 60
  • 3–10 min 3% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=10
  • 100% W n=9
  • 100% T n=8
  • 100% F n=7
  • 100% S n=11
  • 89% S n=9

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
13:51on time on time
14:02 / 14:04≈ on time ≈ on time
14:18≈ on time ≈ +1 min
14:23 / 14:25≈ on time ≈ +1 min
14:34≈ on time ≈ +1 min
14:40on 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
Tue 17 NovAmsterdam Sloterdijk 14:48Partial coverage0 min—
Mon 16 NovAmsterdam Sloterdijk 14:53+3 min+4 min
Sun 15 NovAmsterdam Sloterdijk 14:49+1 min+1 min
Sat 14 NovAmsterdam Sloterdijk 14:490 min—
Fri 13 NovAmsterdam Sloterdijk 14:49+1 min—
Thu 12 NovAmsterdam Sloterdijk 14:49Partial coverage+2 min+3 min
Wed 11 NovAmsterdam Sloterdijk 14:49Partial coverage+1 min—
Tue 10 NovAmsterdam Sloterdijk 14:49Partial coverage+1 min—
Mon 9 NovAmsterdam Sloterdijk 14:49Partial coverage+1 min—
Sun 8 NovAmsterdam Sloterdijk 14:53+4 min+5 min
Sat 7 NovAmsterdam Sloterdijk 14:49+1 min—
Fri 6 NovAmsterdam Sloterdijk 14:49No data—
Thu 5 NovAmsterdam Sloterdijk 14:49No data—
Wed 4 NovAmsterdam Sloterdijk 14:49Partial coverage+1 min—
Tue 3 NovAmsterdam Sloterdijk 14:49No data—
Mon 2 NovAmsterdam Sloterdijk 14:49Partial coverage0 min—
Sun 1 NovAmsterdam Sloterdijk 14:510 min+2 min
Sat 31 OctAmsterdam Sloterdijk 14:51+2 min+3 min
Fri 30 OctAmsterdam Sloterdijk 14:49No data—
Thu 29 OctAmsterdam Sloterdijk 14:49Partial coverage0 min—
Wed 28 OctAmsterdam Sloterdijk 14:49Partial coverage0 min—
Tue 27 OctAmsterdam Sloterdijk 14:49No data—
Mon 26 OctAmsterdam Sloterdijk 14:49No data—
Sun 25 OctAmsterdam Sloterdijk 14:49No data—
Sat 24 OctAmsterdam Sloterdijk 14:50+1 min—
Fri 23 OctAmsterdam Sloterdijk 14:500 min—
Thu 22 OctAmsterdam Sloterdijk 14:49Partial coverage0 min—
Wed 21 OctAmsterdam Sloterdijk 14:49No data—
Tue 20 OctAmsterdam Sloterdijk 14:50Partial coverage0 min—
Mon 19 OctAmsterdam Sloterdijk 14:49No data—