Train NS 580 Groningen – Den Haag Centraal

Groningen 21:18 → Den Haag Centraal 23:50 Daily 2 h 32 min · 7 stops NS (Nederlandse Spoorwegen)

It has not run yet today

Last recorded run: Friday 6 November +4 min

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

Next departure 21:18 today · Groningen
On-time · 30 days
94%
17/18 runs under 3 min
RT coverage: 16 full · 2 partial · 9 no data
On-time · 90 days
95%
21/22 runs under 3 min
RT coverage: 20 full · 2 partial · 25 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: +2 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

  • Fri 6 Nov Max en route +5 min · last fix heading to — +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 21
  • 3–10 min 5% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 22 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
21:18on time on time
21:35≈ on time ≈ on time
22:14 / 22:19≈ on time ≈ +1 min
22:54 / 22:56≈ on time ≈ +1 min
23:09 / 23:13≈ on time ≈ +1 min
23:31 / 23:33≈ on time ≈ +2 min
23:50on 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
Fri 6 Nov— 23:58+4 min+5 min
Thu 5 Nov— 23:52No data—
Wed 4 Nov— 23:53+1 min+2 min
Tue 3 Nov— 23:52No data—
Sun 1 NovGouda 23:53+1 min+3 min
Sat 31 OctUtrecht Centraal 23:51Partial coverage0 min—
Fri 30 Oct— 23:510 min—
Thu 29 Oct— 23:56+3 min+5 min
Wed 28 Oct— 23:580 min—
Tue 27 Oct— 00:100 min—
Mon 26 Oct— 23:51No data—
Sun 25 OctGouda 23:52No data—
Sat 24 OctZwolle 23:540 min—
Fri 23 Oct— 23:590 min+4 min
Thu 22 Oct— 00:04No data—
Wed 21 Oct— 00:00No data—
Mon 19 Oct— 22:080 min—
Sun 18 OctUtrecht Overvecht 23:52+1 min—
Sat 17 OctUtrecht Overvecht 23:52No data—
Fri 16 Oct— 23:510 min—
Thu 15 Oct— 23:51No data—
Wed 14 Oct— 23:520 min—
Tue 13 Oct— 23:56No data—
Mon 12 Oct— 23:52+1 min+1 min
Sun 11 OctGouda 23:510 min—
Sat 10 OctAssen 23:53Partial coverage+1 min—
Fri 9 Oct— 23:510 min—
Thu 8 Oct— 23:53+1 min—
Wed 7 Oct— 23:54+2 min+3 min
Tue 6 Oct— 23:510 min—