Train NS 531 Den Haag Centraal – Groningen

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

Running now · updated 10:12

Heading to Groningen 0 min

Estimated arrival at Groningen 11:42 · 126 km/h

  1. Den Haag Centraal09:10
  2. Gouda09:27
  3. Utrecht Centraal09:47
  4. Amersfoort Centraal10:04
  5. Zwolle10:41
  6. Assen11:25
  7. Groningen11:42

Today it is running no worse than usual: typical arrival delay is 0 min; 96% of the last 24 runs arrived on time.

On-time · 30 days
96%
23/24 runs under 3 min
RT coverage: 12 full · 12 partial · 6 no data
On-time · 90 days
97%
35/36 runs under 3 min
RT coverage: 20 full · 16 partial · 53 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

Worst days

  • Tue 10 Nov Max en route +20 min · last fix heading to Assen +20 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 97% · 35
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 83% T n=6
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=6
  • 100% S n=5

Stops and timetable

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

Last 90 days, 36 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 10Today
09:10on time on time
09:27 / 09:29≈ on time ≈ on time
09:47 / 09:51≈ on time ≈ on time
10:04 / 10:06≈ on time ≈ on time
10:41 / 10:46≈ on time ≈ +1 min
11:25≈ on time ≈ +1 min
11: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
Thu 19 NovAmersfoort Centraal 10:09Partial coverage0 min—
Wed 18 NovAssen 11:440 min—
Tue 17 NovAssen 11:43Partial coverage0 min—
Mon 16 NovAssen 11:44Partial coverage0 min+1 min
Sun 15 NovAssen 11:44+2 min+2 min
Sat 14 NovAssen 11:430 min—
Fri 13 NovAssen 11:430 min—
Thu 12 NovAssen 11:44Partial coverage0 min—
Wed 11 NovAssen 11:44Partial coverage+1 min+1 min
Tue 10 NovAssen 12:14Partial coverage+20 min+20 min
Mon 9 NovAssen 11:43Partial coverage0 min—
Sun 8 NovAssen 11:44+1 min+1 min
Sat 7 NovAssen 11:44+1 min+1 min
Fri 6 NovAssen 11:54No data—
Thu 5 NovAssen 11:44No data—
Wed 4 NovAssen 11:44Partial coverage0 min—
Tue 3 NovAssen 12:03No data—
Mon 2 NovAssen 11:39Partial coverage0 min—
Sun 1 NovAssen 11:440 min—
Sat 31 OctAssen 11:430 min—
Fri 30 OctAssen 11:400 min—
Thu 29 OctAssen 11:58Partial coverage0 min—
Wed 28 OctAssen 11:42Partial coverage0 min—
Tue 27 OctAssen 11:44Partial coverage0 min—
Mon 26 OctAssen 11:44No data—
Sun 25 OctAssen 11:44No data—
Sat 24 OctAssen 11:44+1 min+1 min
Fri 23 OctAssen 11:440 min—
Thu 22 OctAssen 11:500 min—
Wed 21 OctAssen 11:40No data—