Train NS 653 Den Haag Centraal – Leeuwarden

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 14:40 from Den Haag Centraal · Tue 10 Nov

Next departure 14:40 today · Den Haag Centraal
On-time · 30 days
100%
19/19 runs under 3 min
RT coverage: 13 full · 6 partial · 10 no data
On-time · 90 days
96%
25/26 runs under 3 min
RT coverage: 17 full · 9 partial · 62 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Thu 8 Oct Max en route +8 min · last fix heading to Heerenveen +8 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 96% · 25
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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