Train NS 523 Den Haag Centraal – Groningen

Den Haag Centraal 07:08 → Groningen 09:42 Daily 2 h 34 min · 8 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Assen at 09:44 0 min

  1. Den Haag Centraal07:08
  2. Lansingerland-Zoetermeer07:18
  3. Gouda07:28
  4. Amersfoort Centraal08:04
  5. Zwolle08:41
  6. Assen09:25
  7. Groningen09:42

Next service: tomorrow 07:08 from Den Haag Centraal · Sun 8 Nov

Next departure 07:08 tomorrow · Den Haag Centraal
On-time · 30 days
88%
22/25 runs under 3 min
RT coverage: 24 full · 1 partial · 5 no data
On-time · 90 days
86%
24/28 runs under 3 min
RT coverage: 27 full · 1 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Sun 11 Oct Max en route +6 min · last fix heading to Assen +5 min
  • Thu 8 Oct Max en route +5 min · last fix heading to Assen +5 min
  • Wed 4 Nov Max en route +5 min · last fix heading to Assen +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Amersfoort Centraal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 24
  • 3–10 min 14% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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