Train NS 677 Den Haag Centraal – Leeuwarden

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

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 20:40 from Den Haag Centraal · Thu 5 Nov

Next departure 20:40 today · Den Haag Centraal
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 17 full · 2 partial · 9 no data
On-time · 90 days
90%
19/21 runs under 3 min
RT coverage: 19 full · 2 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: +1 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

  • Tue 6 Oct Max en route +5 min · last fix heading to — +5 min
  • Fri 23 Oct Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 19
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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