Train NS 555 Den Haag Centraal – Groningen

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

Running now · updated 15:29

Heading to Groningen 0 min

Estimated arrival at Groningen 17:42 · 2 km/h

  1. Den Haag Centraal15:10
  2. Gouda15:27
  3. Utrecht Centraal15:47
  4. Amersfoort Centraal16:04
  5. Zwolle16:41
  6. Assen17:25
  7. Groningen17:42

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

On-time · 30 days
85%
23/27 runs under 3 min
RT coverage: 19 full · 8 partial · 3 no data
On-time · 90 days
88%
35/40 runs under 3 min
RT coverage: 29 full · 11 partial · 49 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Wed 11 Nov Max en route +19 min · last fix heading to Assen +19 min
  • Fri 13 Nov Max en route +6 min · last fix heading to Assen +6 min
  • Sun 11 Oct Max en route +6 min · last fix heading to Assen +6 min
  • Thu 12 Nov Max en route +5 min · last fix heading to Assen +5 min
  • Mon 26 Oct Max en route +4 min · last fix heading to Assen +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 86% M n=7
  • 100% T n=6
  • 86% W n=7
  • 75% T n=4
  • 83% F n=6
  • 100% S n=5
  • 80% S n=5

Stops and timetable

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

Last 90 days, 40 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
15:10on time on time
15:27 / 15:29≈ on time ≈ on time
15:47 / 15:51≈ on time ≈ +1 min
16:04 / 16:06≈ on time ≈ +1 min
16:41 / 16:46≈ on time ≈ +2 min
17:25≈ on time ≈ +3 min
17: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
Wed 18 NovGouda 15:24Partial coverage0 min—
Tue 17 NovAssen 17:44Partial coverage+1 min+2 min
Mon 16 NovAssen 17:50+2 min+2 min
Sun 15 NovAssen 17:48+2 min+3 min
Sat 14 NovAssen 17:430 min—
Fri 13 NovAssen 17:54+6 min+6 min
Thu 12 NovAssen 17:49Partial coverage+5 min+5 min
Wed 11 NovAssen 18:14Partial coverage+19 min+19 min
Tue 10 NovAssen 17:44Partial coverage+2 min+2 min
Mon 9 NovAssen 17:44+2 min+2 min
Sun 8 NovAssen 17:440 min—
Sat 7 NovAssen 17:44+1 min+1 min
Fri 6 NovAssen 17:440 min—
Thu 5 NovAssen 17:48Partial coverage0 min—
Wed 4 NovAssen 17:44Partial coverage0 min—
Tue 3 NovAssen 17:390 min—
Mon 2 NovAssen 17:390 min—
Sun 1 NovAssen 17:440 min—
Sat 31 OctAssen 17:43+2 min+2 min
Fri 30 OctZwolle 17:430 min—
Thu 29 OctGouda 17:43No data—
Wed 28 OctAssen 17:43Partial coverage0 min—
Tue 27 OctAssen 17:55No data—
Mon 26 OctAssen 17:51+4 min+4 min
Sun 25 OctAssen 17:44No data—
Sat 24 OctAssen 17:430 min—
Fri 23 OctAssen 17:430 min—
Thu 22 OctAssen 17:550 min—
Wed 21 OctAssen 17:440 min—
Tue 20 OctAssen 17:390 min—