Train NS 670 Leeuwarden – Den Haag Centraal

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:46 from Leeuwarden · Sat 7 Nov

Next departure 18:46 today · Leeuwarden
On-time · 30 days
88%
14/16 runs under 3 min
RT coverage: 9 full · 7 partial · 12 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 13 full · 7 partial · 46 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 11 Oct Max en route +20 min · last fix heading to Gouda +19 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Zwolle +4 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 90% · 18
  • 3–10 min 5% · 1
  • 10–30 min 5% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=2
  • 100% T n=3
  • 75% F n=4
  • 100% S n=2
  • 67% 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
18:46on time on time
19:02≈ on time ≈ on time
19:16≈ on time ≈ on time
19:26≈ on time ≈ on time
19:41 / 19:49≈ on time ≈ +1 min
20:24 / 20:26≈ on time ≈ +1 min
20:39 / 20:43≈ on time ≈ +1 min
21:01 / 21:03≈ on time ≈ +1 min
21:20on time +2 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 6 NovLeeuwarden 21:19Partial coverage0 min—
Thu 5 Nov— 19:42No data—
Wed 4 Nov— 19:43No data—
Tue 3 Nov— 21:20No data—
Sun 1 NovGouda 21:19Partial coverage0 min—
Sat 31 OctGouda 21:17Partial coverage0 min—
Fri 30 OctLeeuwarden 21:21No data—
Thu 29 Oct— 21:26+2 min+3 min
Wed 28 Oct— 21:260 min—
Tue 27 Oct— 21:220 min—
Mon 26 OctZwolle 21:25Partial coverage0 min—
Sun 25 OctGouda 21:23No data—
Sat 24 OctGouda 21:22No data—
Fri 23 OctMeppel 21:24Partial coverage+2 min+2 min
Thu 22 Oct— 21:240 min—
Wed 21 Oct— 21:23No data—
Tue 20 OctLeeuwarden 21:22No data—
Mon 19 Oct— 20:460 min—
Sun 18 OctUtrecht Overvecht 21:220 min—
Sat 17 OctUtrecht Overvecht 21:22No data—
Fri 16 OctZwolle 21:28+4 min+4 min
Thu 15 Oct— 21:26No data—
Wed 14 OctZwolle 21:22No data—
Tue 13 Oct— 21:28No data—
Mon 12 Oct— 21:220 min—
Sun 11 OctGouda 22:00Partial coverage+19 min+20 min
Sat 10 OctGouda 21:22Partial coverage0 min—
Fri 9 Oct— 21:210 min—
Thu 8 Oct— 21:360 min—
Wed 7 Oct— 01:160 min—