Train NS 657 Den Haag Centraal – Leeuwarden

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

It has not run yet today

Last recorded run: Tuesday 10 November +4 min

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

Next departure 15:40 today · Den Haag Centraal
On-time · 30 days
89%
17/19 runs under 3 min
RT coverage: 14 full · 5 partial · 10 no data
On-time · 90 days
81%
22/27 runs under 3 min
RT coverage: 18 full · 9 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +3 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 9 Nov Max en route +14 min · last fix heading to Heerenveen +14 min
  • Wed 7 Oct Max en route +12 min · last fix heading to Heerenveen +12 min
  • Tue 6 Oct Max en route +8 min · last fix heading to Heerenveen +8 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Heerenveen +4 min
  • Mon 5 Oct Max en route +5 min · last fix heading to Heerenveen +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 22
  • 3–10 min 11% · 3
  • 10–30 min 7% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=6
  • 60% T n=5
  • 67% W n=3
  • 100% T n=2
  • 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, 27 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
15:40on time on time
15:58 / 15:59≈ on time ≈ on time
16:17 / 16:21≈ on time ≈ +1 min
16:34 / 16:36≈ on time ≈ +1 min
17:11 / 17:18≈ on time ≈ +2 min
17:34≈ on time ≈ +2 min
17:44≈ on time ≈ +2 min
17:57≈ on time ≈ +3 min
18:14on time +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 NovHeerenveen 18:09Partial coverage+4 min+4 min
Mon 9 NovHeerenveen 18:43+14 min+14 min
Sun 8 NovHeerenveen 18:140 min—
Sat 7 NovHeerenveen 18:19+3 min+3 min
Fri 6 NovHeerenveen 18:14Partial coverage0 min—
Thu 5 NovHeerenveen 18:14No data—
Wed 4 NovHeerenveen 18:39Partial coverage0 min—
Tue 3 NovHeerenveen 18:14No data—
Mon 2 NovHeerenveen 18:140 min—
Sun 1 NovHeerenveen 18:16Partial coverage+1 min—
Sat 31 OctHeerenveen 18:120 min—
Fri 30 OctHeerenveen 18:15No data—
Thu 29 OctHeerenveen 18:16No data—
Wed 28 OctHeerenveen 18:16No data—
Tue 27 OctHeerenveen 18:16Partial coverage0 min—
Mon 26 OctHeerenveen 18:16+1 min—
Sun 25 OctWolvega 18:07No data—
Sat 24 OctWolvega 18:060 min—
Fri 23 OctHeerenveen 18:380 min—
Thu 22 OctZwolle 18:150 min—
Wed 21 OctHeerenveen 18:16No data—
Tue 20 OctHeerenveen 18:160 min—
Mon 19 OctHeerenveen 18:160 min—
Sun 18 OctHeerenveen 18:20+3 min+3 min
Sat 17 OctHeerenveen 18:12No data—
Fri 16 OctHeerenveen 18:16No data—
Thu 15 OctHeerenveen 18:18No data—
Wed 14 OctHeerenveen 18:160 min—
Tue 13 OctHeerenveen 18:150 min—
Mon 12 OctHeerenveen 18:150 min—