Train NS 552 Groningen → Den Haag Centraal

Groningen 14:18 → Den Haag Centraal 16:52 Daily 2 h 34 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 20 November +3 min

Next service: today 14:18 from Groningen · Sat 21 Nov

Next departure 14:18 today · Groningen
On-time · 30 days
80%
16/20 runs under 3 min
RT coverage: 5 full · 15 partial · 9 no data
On-time · 90 days
87%
27/31 runs under 3 min
RT coverage: 9 full · 22 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

Worst days

  • Thu 19 Nov Max en route +8 min · last fix heading to Gouda +8 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Gouda +4 min
  • Mon 16 Nov Max en route +4 min · last fix heading to Gouda +4 min
  • Fri 20 Nov Max en route +3 min · last fix heading to Gouda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 87% · 27
  • 3–10 min 13% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 83% M n=6
  • 100% T n=3
  • 100% W n=5
  • 75% T n=4
  • 67% F n=3
  • 80% S n=5
  • 100% S n=5

Stops and timetable

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

Last 90 days, 31 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:18on time on time
14:35≈ on time ≈ on time
15:14 / 15:19≈ on time ≈ on time
15:54 / 15:56≈ on time ≈ +1 min
16:09 / 16:13≈ on time ≈ +1 min
16:31 / 16:34≈ on time ≈ +1 min
16:52on 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
Fri 20 NovGouda 16:59Partial coverage+3 min+3 min
Thu 19 NovGouda 16:48Partial coverage+8 min+8 min
Wed 18 NovGouda 16:54+1 min+2 min
Tue 17 NovGouda 16:54Partial coverage0 min+2 min
Mon 16 NovGouda 16:58Partial coverage+4 min+4 min
Sun 15 NovGouda 16:540 min—
Sat 14 NovGouda 16:53Partial coverage0 min—
Fri 13 NovGouda 16:54Partial coverage0 min—
Thu 12 NovGouda 16:59Partial coverage+3 min+6 min
Wed 11 NovGouda 16:53Partial coverage0 min—
Tue 10 NovGouda 16:55Partial coverage+1 min+1 min
Mon 9 NovGouda 16:54Partial coverage0 min—
Sun 8 NovLansingerland-Zoetermeer 16:550 min—
Sat 7 NovLansingerland-Zoetermeer 16:570 min—
Fri 6 NovGouda 16:53No data—
Thu 5 NovGouda 17:14No data—
Wed 4 NovGouda 16:54Partial coverage0 min—
Tue 3 NovGouda 16:54No data—
Mon 2 NovGouda 17:07No data—
Sun 1 NovGouda 16:48Partial coverage0 min—
Sat 31 OctGouda 16:53Partial coverage+4 min+4 min
Fri 30 OctGouda 16:53No data—
Thu 29 OctGouda 16:56No data—
Wed 28 OctGouda 16:54Partial coverage0 min—
Tue 27 OctGouda 16:54No data—
Mon 26 OctGouda 16:53Partial coverage0 min—
Sun 25 OctGouda 16:52No data—
Sat 24 OctGouda 16:52+1 min+1 min
Fri 23 OctGouda 16:52No data—
Thu 22 OctGouda 16:54No data—