Train NS 563 Den Haag Centraal – Groningen

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

It has not run yet today

Last recorded run: Monday 9 November 0 min

Next service: today 17:10 from Den Haag Centraal · Tue 10 Nov

Next departure 17:10 today · Den Haag Centraal
On-time · 30 days
89%
16/18 runs under 3 min
RT coverage: 10 full · 8 partial · 11 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 12 full · 13 partial · 63 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

  • Fri 23 Oct Max en route +7 min · last fix heading to Assen +7 min
  • Sat 31 Oct Max en route +4 min · last fix heading to Assen +4 min

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 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=2
  • 100% W n=3
  • 100% T n=3
  • 67% F n=3
  • 75% S n=4
  • 100% S n=4

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
17:10on time on time
17:28 / 17:29≈ on time ≈ on time
17:47 / 17:51≈ on time ≈ +1 min
18:04 / 18:06≈ on time ≈ +1 min
18:41 / 18:46≈ on time ≈ +2 min
19:25≈ on time ≈ +3 min
19:42on time +3 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 NovAmersfoort Centraal 19:44Partial coverage0 min—
Sun 8 NovAssen 19:440 min—
Sat 7 NovAssen 19:430 min—
Fri 6 NovZwolle 19:43Partial coverage0 min—
Thu 5 NovAmersfoort Centraal 19:49No data—
Wed 4 NovAmersfoort Centraal 19:44Partial coverage0 min—
Tue 3 NovAmersfoort Centraal 19:44Partial coverage0 min—
Mon 2 NovAmersfoort Centraal 19:44Partial coverage0 min—
Sun 1 NovAssen 19:390 min—
Sat 31 OctAssen 19:49+4 min+4 min
Fri 30 OctZwolle 19:43No data—
Thu 29 OctUtrecht Centraal 19:43Partial coverage0 min—
Wed 28 OctAmersfoort Centraal 19:46Partial coverage0 min—
Tue 27 OctUtrecht Centraal 19:44No data—
Mon 26 OctAmersfoort Centraal 19:52Partial coverage0 min—
Sun 25 OctAssen 19:44No data—
Sat 24 OctAssen 19:510 min—
Fri 23 OctAssen 19:55+7 min+7 min
Thu 22 OctAmersfoort Centraal 19:44No data—
Wed 21 OctAmersfoort Centraal 19:44No data—
Tue 20 OctZwolle 19:43No data—
Mon 19 OctAmersfoort Centraal 19:440 min—
Sun 18 OctAssen 19:440 min—
Sat 17 OctAssen 19:44No data—
Fri 16 OctAssen 19:45No data—
Thu 15 OctAmersfoort Centraal 19:460 min—
Wed 14 OctGouda 19:46No data—
Tue 13 OctAmersfoort Centraal 19:46No data—
Mon 12 OctAmersfoort Centraal 19:460 min—
Sun 11 OctAssen 19:430 min—