Train NS 576 Groningen – Den Haag Centraal

Groningen 20:18 → Den Haag Centraal 22:52 Daily 2 h 34 min · 8 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 20:18 from Groningen · Sun 8 Nov

Next departure 20:18 today · Groningen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 17 full · 1 partial · 10 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 22 full · 1 partial · 29 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: +1 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

  • Mon 12 Oct Max en route +25 min · last fix heading to — +24 min
  • Fri 9 Oct Max en route +6 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 4% · 1
  • 10–30 min 4% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 23 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
20:18on time on time
20:35≈ on time ≈ on time
21:14 / 21:19≈ on time ≈ on time
21:54 / 21:56≈ on time ≈ +1 min
22:09 / 22:13≈ on time ≈ +1 min
22:31 / 22:33≈ on time ≈ +1 min
22:42≈ on time ≈ +1 min
22: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
Sat 7 NovLansingerland-Zoetermeer 22:54Partial coverage0 min—
Fri 6 Nov— 22:530 min—
Thu 5 Nov— 22:54No data—
Wed 4 Nov— 22:530 min—
Mon 2 Nov— 22:530 min—
Sun 1 NovZwolle 22:490 min—
Sat 31 OctGouda 22:510 min—
Fri 30 Oct— 22:550 min—
Thu 29 Oct— 22:530 min—
Wed 28 Oct— 22:54No data—
Tue 27 Oct— 22:54No data—
Mon 26 Oct— 22:590 min—
Sun 25 OctGouda 22:51No data—
Sat 24 OctGouda 22:580 min—
Fri 23 Oct— 22:55+1 min+2 min
Thu 22 Oct— 22:53No data—
Wed 21 Oct— 23:07No data—
Tue 20 Oct— 22:53No data—
Mon 19 Oct— 22:150 min—
Sun 18 OctUtrecht Overvecht 22:52+1 min—
Sat 17 OctUtrecht Overvecht 22:52No data—
Fri 16 Oct— 22:540 min—
Thu 15 Oct— 22:530 min—
Wed 14 Oct— 22:53No data—
Tue 13 Oct— 23:06No data—
Mon 12 Oct— 23:42+24 min+25 min
Sun 11 OctGouda 22:52+1 min+6 min
Sat 10 OctAmersfoort Centraal 22:520 min—
Fri 9 Oct— 23:04+4 min+6 min
Thu 8 Oct— 22:53+1 min—