Train NS 4250 Den Haag Centraal – Amsterdam Centraal

Den Haag Centraal 16:25 → Amsterdam Centraal 17:35 Daily 1 h 10 min · 14 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Wednesday 4 November No data

Next service: today 16:25 from Den Haag Centraal · Thu 5 Nov

Next departure 16:25 today · Den Haag Centraal
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 15 full · 1 partial · 11 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 17 full · 1 partial · 62 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 Amsterdam 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 18 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
16:25on time on time
16:28≈ on time ≈ on time
16:31≈ on time ≈ on time
16:36≈ on time ≈ on time
16:39≈ on time ≈ on time
16:43 / 16:51≈ on time ≈ on time
16:56≈ on time ≈ on time
17:04≈ on time ≈ on time
17:10≈ on time ≈ on time
17:15 / 17:17≈ on time ≈ on time
17:20≈ on time ≈ on time
17:25≈ on time ≈ on time
17:30≈ on time ≈ +1 min
17:35on 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 4 NovAmsterdam Sloterdijk 17:44No data—
Tue 3 NovAmsterdam Sloterdijk 17:44No data—
Mon 2 NovAmsterdam Sloterdijk 17:44Partial coverage0 min—
Sun 1 NovHeemstede-Aerdenhout 17:220 min—
Sat 31 OctHeemstede-Aerdenhout 17:220 min—
Fri 30 OctHeemstede-Aerdenhout 17:220 min—
Thu 29 OctHeemstede-Aerdenhout 17:22No data—
Wed 28 OctHeemstede-Aerdenhout 17:220 min—
Tue 27 OctHeemstede-Aerdenhout 17:220 min—
Mon 26 OctHeemstede-Aerdenhout 17:22No data—
Sun 25 OctHeemstede-Aerdenhout 17:22No data—
Sat 24 OctHeemstede-Aerdenhout 17:220 min—
Fri 23 OctHeemstede-Aerdenhout 17:23No data—
Thu 22 OctHeemstede-Aerdenhout 17:220 min—
Wed 21 OctHeemstede-Aerdenhout 17:17No data—
Tue 20 OctHeemstede-Aerdenhout 17:230 min—
Mon 19 OctHeemstede-Aerdenhout 17:22No data—
Sun 18 OctHeemstede-Aerdenhout 17:230 min—
Sat 17 OctHeemstede-Aerdenhout 17:240 min—
Fri 16 OctHeemstede-Aerdenhout 17:220 min—
Thu 15 OctHeemstede-Aerdenhout 17:23No data—
Wed 14 OctHeemstede-Aerdenhout 17:26No data—
Tue 13 OctHeemstede-Aerdenhout 17:24No data—
Mon 12 OctHeemstede-Aerdenhout 17:220 min—
Fri 9 OctHeemstede-Aerdenhout 17:230 min—
Thu 8 OctVoorhout 17:34+2 min+3 min
Wed 7 OctHeemstede-Aerdenhout 17:220 min—
Tue 6 OctHeemstede-Aerdenhout 17:220 min—
Mon 5 OctHeemstede-Aerdenhout 17:22+1 min—
Sun 4 OctHeemstede-Aerdenhout 17:22No data—