Train NS 650 Leeuwarden – Den Haag Centraal

Leeuwarden 13:46 → Den Haag Centraal 16:20 Daily 2 h 34 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 13:46 from Leeuwarden · Fri 6 Nov

Next departure 13:46 today · Leeuwarden
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 8 full · 9 partial · 12 no data
On-time · 90 days
95%
19/20 runs under 3 min
RT coverage: 9 full · 11 partial · 68 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

  • Wed 7 Oct Max en route +8 min · last fix heading to Gouda +8 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 19
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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:46on time on time
14:02≈ on time ≈ on time
14:16≈ on time ≈ on time
14:26≈ on time ≈ on time
14:41 / 14:49≈ on time ≈ on time
15:24 / 15:26≈ on time ≈ on time
15:39 / 15:43≈ on time ≈ on time
16:01 / 16:03≈ on time ≈ on time
16:20on time on time

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
Thu 5 NovGouda 16:22No data—
Wed 4 NovGouda 16:19Partial coverage0 min—
Tue 3 NovGouda 16:19No data—
Mon 2 NovGouda 16:28No data—
Sun 1 NovGouda 16:22Partial coverage0 min—
Sat 31 OctGouda 16:21Partial coverage0 min—
Fri 30 OctGouda 16:23No data—
Thu 29 OctGouda 16:22Partial coverage0 min—
Wed 28 OctGouda 16:23Partial coverage0 min—
Tue 27 OctGouda 16:240 min—
Mon 26 OctGouda 16:21No data—
Sun 25 OctGouda 16:27No data—
Sat 24 OctGouda 16:210 min—
Fri 23 OctGouda 16:24No data—
Thu 22 OctGouda 16:32No data—
Wed 21 OctGouda 16:23No data—
Tue 20 OctGouda 16:24No data—
Mon 19 OctAmersfoort Centraal 15:450 min—
Sun 18 OctUtrecht Overvecht 16:220 min—
Sat 17 OctUtrecht Overvecht 16:230 min—
Fri 16 OctGouda 16:220 min—
Thu 15 OctGouda 16:380 min—
Wed 14 OctGouda 16:35No data—
Tue 13 OctGouda 16:26No data—
Mon 12 OctGouda 16:220 min—
Sun 11 OctGouda 16:21Partial coverage0 min—
Sat 10 OctGouda 16:24Partial coverage+2 min+2 min
Fri 9 OctGouda 16:21Partial coverage0 min—
Thu 8 OctGouda 16:22Partial coverage+1 min+3 min
Wed 7 OctGouda 16:36Partial coverage+8 min+8 min