Train NS 682 Leeuwarden – Den Haag Centraal

Leeuwarden 21:46 → Den Haag Centraal 00:20 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 21:46 from Leeuwarden · Thu 5 Nov

Next departure 21:46 today · Leeuwarden
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 18 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 30 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
21:46on time on time
22:02≈ on time ≈ on time
22:16≈ on time ≈ on time
22:26≈ on time ≈ on time
22:41 / 22:49≈ on time ≈ on time
23:24 / 23:26≈ on time ≈ on time
23:39 / 23:43≈ on time ≈ on time
00:01 / 00:03≈ on time ≈ on time
00: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
Wed 4 Nov— 00:220 min—
Tue 3 Nov— 00:220 min—
Mon 2 Nov— 00:190 min—
Sun 1 NovGouda 00:170 min—
Sat 31 OctZwolle 00:220 min—
Thu 29 Oct— 00:320 min+4 min
Wed 28 Oct— 00:220 min—
Tue 27 Oct— 00:220 min—
Mon 26 Oct— 00:220 min—
Sun 25 OctGouda 00:220 min—
Sat 24 OctMeppel 00:240 min—
Fri 23 Oct— 00:330 min+6 min
Thu 22 Oct— 00:210 min—
Wed 21 Oct— 00:230 min—
Tue 20 Oct— 00:260 min—
Mon 19 Oct— 22:280 min—
Sun 18 OctUtrecht Overvecht 00:230 min—
Sat 17 OctUtrecht Overvecht 00:220 min—
Fri 16 Oct— 00:250 min—
Thu 15 Oct— 00:220 min—
Wed 14 Oct— 00:220 min—
Tue 13 Oct— 00:220 min—
Mon 12 Oct— 00:210 min—
Sun 11 OctGouda 00:260 min+2 min
Sat 10 OctHeerenveen 00:240 min—
Fri 9 Oct— 00:220 min—
Thu 8 Oct— 01:180 min+17 min
Wed 7 Oct— 00:210 min—
Tue 6 Oct— 00:210 min—
Mon 5 OctGouda 00:26Partial coverage0 min+3 min