Train NS 551 Den Haag Centraal – Groningen

Den Haag Centraal 14:10 → Groningen 16:42 Daily 2 h 32 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 14:10 from Den Haag Centraal · Wed 11 Nov

Next departure 14:10 today · Den Haag Centraal
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 9 full · 8 partial · 12 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 11 full · 14 partial · 63 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 Groningen, 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 +7 min · last fix heading to Assen +7 min
  • Sat 10 Oct Max en route +7 min · last fix heading to Assen +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 25 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:10on time on time
14:27 / 14:29≈ on time ≈ on time
14:47 / 14:51≈ on time ≈ on time
15:04 / 15:06≈ on time ≈ on time
15:41 / 15:46≈ on time ≈ on time
16:25≈ on time ≈ on time
16:42on 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
Tue 10 NovAssen 16:43Partial coverage0 min—
Mon 9 NovAssen 16:44Partial coverage0 min—
Sun 8 NovAssen 16:440 min—
Sat 7 NovAssen 16:430 min—
Fri 6 NovAssen 16:48No data—
Thu 5 NovAssen 16:44Partial coverage0 min—
Wed 4 NovAssen 16:48Partial coverage+2 min+6 min
Tue 3 NovAssen 16:39No data—
Mon 2 NovAssen 16:44No data—
Sun 1 NovAssen 16:48Partial coverage+2 min+3 min
Sat 31 OctAssen 16:39Partial coverage0 min—
Fri 30 OctAssen 16:480 min—
Thu 29 OctAssen 16:52No data—
Wed 28 OctAssen 16:42No data—
Tue 27 OctAssen 16:46Partial coverage0 min—
Mon 26 OctAssen 16:43Partial coverage0 min—
Sun 25 OctAssen 16:52No data—
Sat 24 OctAssen 16:44+1 min+1 min
Fri 23 OctAssen 16:45No data—
Thu 22 OctAssen 16:430 min—
Wed 21 OctAssen 16:44No data—
Tue 20 OctAssen 16:440 min—
Mon 19 OctAssen 16:430 min—
Sun 18 OctAssen 16:430 min—
Sat 17 OctAssen 16:390 min—
Fri 16 OctAssen 16:56No data—
Thu 15 OctAssen 16:43No data—
Wed 14 OctAssen 16:44No data—
Tue 13 OctAssen 16:43No data—
Mon 12 OctAssen 16:440 min—