Train NS 673 Den Haag Centraal – Leeuwarden

Den Haag Centraal 19:40 → Leeuwarden 22:14 Daily 2 h 34 min · 9 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 19:40 from Den Haag Centraal · Wed 11 Nov

Next departure 19:40 today · Den Haag Centraal
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 9 no data
On-time · 90 days
92%
24/26 runs under 3 min
RT coverage: 23 full · 3 partial · 28 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: +2 min

Last 30 days

Arrival delay at Leeuwarden, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 12 Oct Max en route +20 min · last fix heading to — +20 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 24
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 75% F n=4
  • 100% S n=5
  • 100% S n=4

Stops and timetable

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

Last 90 days, 26 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
19:40on time on time
19:57 / 19:59≈ on time ≈ on time
20:17 / 20:21≈ on time ≈ +1 min
20:34 / 20:36≈ on time ≈ +1 min
21:11 / 21:18≈ on time ≈ +2 min
21:34≈ on time ≈ +2 min
21:44≈ +1 min ≈ +2 min
21:57≈ +1 min ≈ +2 min
22:14+1 min +3 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 10 Nov— 22:140 min—
Mon 9 Nov— 22:140 min—
Sun 8 NovHeerenveen 22:14+1 min—
Sat 7 NovHeerenveen 22:19+3 min+4 min
Fri 6 Nov— 22:14+1 min—
Thu 5 Nov— 22:14No data—
Wed 4 Nov— 22:18+1 min+2 min
Tue 3 Nov— 22:14No data—
Mon 2 Nov— 22:18+2 min+2 min
Sun 1 NovHeerenveen 22:14Partial coverage0 min—
Sat 31 OctHeerenveen 22:21+2 min+2 min
Thu 29 Oct— 22:150 min+1 min
Wed 28 Oct— 22:150 min—
Tue 27 Oct— 22:16No data—
Mon 26 OctGouda 22:20Partial coverage0 min—
Sun 25 OctWolvega 22:06No data—
Sat 24 OctWolvega 22:150 min—
Fri 23 Oct— 22:26+5 min+5 min
Thu 22 Oct— 22:44No data—
Wed 21 Oct— 22:15No data—
Mon 19 Oct— 22:320 min—
Sun 18 OctHeerenveen 22:19+1 min+2 min
Sat 17 OctZwolle 22:160 min—
Fri 16 OctDen Haag Centraal 22:16+1 min+1 min
Thu 15 Oct— 22:15No data—
Wed 14 OctDen Haag Centraal 22:15No data—
Tue 13 Oct— 22:18No data—
Mon 12 Oct— 22:43+20 min+20 min
Sun 11 OctHeerenveen 22:18+1 min+4 min
Sat 10 OctHeerenveen 22:16Partial coverage0 min—