Train NS 579 Den Haag Centraal – Groningen

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

It has not run yet today

Last recorded run: Friday 6 November +1 min

Next service: today 21:10 from Den Haag Centraal · Sat 7 Nov

Next departure 21:10 today · Den Haag Centraal
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 19 full · 2 partial · 6 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 23 full · 2 partial · 22 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 Groningen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

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 100% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=3
  • 100% T n=4
  • 100% F n=4
  • 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, 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
21:10on time on time
21:27 / 21:29≈ on time ≈ on time
21:47 / 21:51≈ on time ≈ on time
22:04 / 22:06≈ on time ≈ on time
22:41 / 22:46≈ on time ≈ +1 min
23:25≈ on time ≈ +1 min
23:42on 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 6 Nov— 23:44+1 min+1 min
Thu 5 Nov— 23:440 min—
Wed 4 Nov— 23:48+2 min+2 min
Tue 3 Nov— 23:440 min—
Sun 1 NovAssen 23:440 min—
Sat 31 OctZwolle 23:00Partial coverage0 min—
Thu 29 Oct— 23:44+1 min+1 min
Wed 28 Oct— 23:44No data—
Tue 27 Oct— 23:430 min—
Mon 26 Oct— 23:43No data—
Sun 25 OctAssen 23:44No data—
Sat 24 OctAmersfoort Centraal 23:430 min—
Fri 23 Oct— 23:50+3 min+4 min
Thu 22 Oct— 23:510 min—
Wed 21 Oct— 23:43No data—
Tue 20 Oct— 23:430 min—
Mon 19 Oct— 22:420 min—
Sun 18 OctAssen 23:430 min—
Sat 17 OctAssen 23:39No data—
Fri 16 Oct— 23:430 min—
Thu 15 Oct— 23:45No data—
Wed 14 Oct— 23:430 min—
Tue 13 Oct— 23:430 min—
Mon 12 Oct— 23:440 min—
Sun 11 OctUtrecht Centraal 22:050 min—
Sat 10 OctUtrecht Centraal 23:44Partial coverage0 min—
Fri 9 Oct— 23:430 min—
Thu 8 Oct— 23:420 min—
Wed 7 Oct— 23:430 min—
Tue 6 Oct— 23:430 min—