Train NS 520 Groningen – Den Haag Centraal

Groningen 06:18 → Den Haag Centraal 08:52 Mon, Tue, Wed, Thu, Fri, Sat 2 h 34 min · 7 stops NS (Nederlandse Spoorwegen)

✓ Today’s run finished

Today, last fix heading to Gouda at 08:54 +2 min

  1. Groningen06:18
  2. Assen06:35
  3. Zwolle07:14
  4. Amersfoort Centraal07:54
  5. Utrecht Centraal08:09
  6. Gouda08:31
  7. Den Haag Centraal08:52

Next service: tomorrow 06:18 from Groningen · Tue 10 Nov

Full trip card
Next departure 06:18 tomorrow · Groningen
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 14 full · 9 partial · 2 no data
On-time · 90 days
100%
28/28 runs under 3 min
RT coverage: 16 full · 12 partial · 48 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: 0 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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=4
  • 100% S n=5
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (7 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
Groningen
06:18on time on time
Assen
06:35≈ on time ≈ on time
Zwolle
07:14 / 07:19≈ on time ≈ on time
Amersfoort Centraal
07:54 / 07:56≈ on time ≈ on time
Utrecht Centraal
08:09 / 08:13≈ on time ≈ on time
Gouda
08:31 / 08:34≈ on time ≈ on time
Den Haag Centraal
08: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
Mon 9 NovGouda 08:54Partial coverage+2 min+2 min
Sat 7 NovLansingerland-Zoetermeer 08:57+1 min+1 min
Fri 6 NovGouda 09:07No data—
Thu 5 NovGouda 08:54Partial coverage0 min—
Wed 4 NovGouda 08:540 min—
Tue 3 NovGouda 09:34Partial coverage0 min—
Mon 2 NovGouda 08:48No data—
Sat 31 OctGouda 08:480 min—
Fri 30 OctAmersfoort Centraal 08:53Partial coverage0 min—
Thu 29 OctGouda 08:56Partial coverage0 min—
Wed 28 OctGouda 08:480 min—
Tue 27 OctGouda 08:48Partial coverage0 min—
Mon 26 OctGouda 09:02Partial coverage0 min—
Sat 24 OctGouda 08:520 min—
Fri 23 OctGouda 08:520 min—
Thu 22 OctGouda 08:54Partial coverage0 min—
Wed 21 OctGouda 08:530 min—
Tue 20 OctGouda 09:06Partial coverage0 min—
Mon 19 OctAmersfoort Centraal 08:130 min—
Sat 17 OctUtrecht Overvecht 08:520 min—
Fri 16 OctGouda 08:530 min—
Thu 15 OctGouda 09:000 min—
Wed 14 OctGouda 08:580 min—
Tue 13 OctGouda 08:480 min—
Mon 12 OctGouda 09:020 min—
Sat 10 OctGouda 08:530 min—
Fri 9 OctGouda 08:56Partial coverage+1 min+2 min
Thu 8 OctGouda 08:54Partial coverage0 min—
Wed 7 OctGouda 08:54+1 min+1 min
Tue 6 OctGouda 08:53Partial coverage0 min—