Train NS 539 Den Haag Centraal – Groningen

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

Running now · updated 10:54

Heading to Groningen No data

Estimated arrival at Groningen 13:42

  1. Den Haag Centraal11:10
  2. Gouda11:27
  3. Utrecht Centraal11:47
  4. Amersfoort Centraal12:04
  5. Zwolle12:41
  6. Assen13:25
  7. Groningen13:42
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 15 full · 2 partial · 12 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 67 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=1
  • 100% W n=3
  • 100% T n=5
  • 100% F n=3
  • 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, 21 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
11:10on time on time
11:27 / 11:29≈ on time ≈ on time
11:47 / 11:51≈ on time ≈ on time
12:04 / 12:06≈ on time ≈ on time
12:41 / 12:46≈ on time ≈ on time
13:25≈ on time ≈ on time
13:42on time on time

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 NovAssen 13:43No data—
Thu 5 NovAssen 13:48Partial coverage0 min—
Wed 4 NovAssen 13:440 min+2 min
Tue 3 NovAssen 13:43No data—
Mon 2 NovAssen 13:44No data—
Sun 1 NovAssen 13:400 min—
Sat 31 OctAssen 13:430 min—
Fri 30 OctAssen 13:390 min—
Thu 29 OctAssen 13:58Partial coverage0 min—
Wed 28 OctAssen 13:430 min—
Tue 27 OctAssen 13:44No data—
Mon 26 OctAssen 13:430 min—
Sun 25 OctAssen 13:43No data—
Sat 24 OctAssen 13:430 min—
Fri 23 OctAssen 13:43No data—
Thu 22 OctAssen 13:430 min—
Wed 21 OctAssen 13:43No data—
Tue 20 OctAssen 13:43No data—
Mon 19 OctZwolle 13:430 min—
Sun 18 OctAssen 13:44+1 min—
Sat 17 OctAssen 13:43No data—
Fri 16 OctAssen 13:440 min—
Thu 15 OctAssen 13:430 min—
Wed 14 OctAssen 13:43No data—
Tue 13 OctAssen 13:43No data—
Mon 12 OctAssen 13:44No data—
Sun 11 OctAssen 13:440 min—
Sat 10 OctAssen 13:430 min—
Fri 9 OctAssen 13:440 min—
Thu 8 OctAssen 13:40Partial coverage+2 min+2 min