Train NS 528 Groningen → Den Haag Centraal

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

NS 528 Groningen–Den Haag Centraal: final delay under 3 min on 20 of its 24 runs with data in the last 30 days (83%). Median final delay: 0 min. TrainsRadar data as of 23 Nov 2026, 00:50 (GMT+1).

It has not run yet today

Last recorded run: Sunday 22 November +1 min

Next service: today 08:18 from Groningen · Mon 23 Nov

Next departure 08:18 today · Groningen
On-time · 30 days
83%
20/24 runs under 3 min
RT coverage: 21 full · 3 partial · 5 no data
On-time · 90 days
89%
34/38 runs under 3 min
RT coverage: 35 full · 3 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +7 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

  • Sat 31 Oct Max en route +29 min · last fix heading to Gouda +29 min
  • Sun 1 Nov Max en route +12 min · last fix heading to Gouda +10 min
  • Fri 20 Nov Max en route +8 min · last fix heading to Gouda +8 min
  • Sun 15 Nov Max en route +7 min · last fix heading to Gouda +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 89% · 34
  • 3–10 min 5% · 2
  • 10–30 min 5% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=4
  • 100% W n=5
  • 100% T n=7
  • 75% F n=4
  • 86% S n=7
  • 67% S n=6

Stops and timetable

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

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