Train Arriva 37558 Groningen – Veendam

Groningen 16:48 → Veendam 17:17 Sun 0 h 29 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Zuidbroek at 17:23 0 min

  1. Groningen16:48
  2. Groningen Europapark16:50
  3. Kropswolde16:59
  4. Martenshoek17:01
  5. Hoogezand-Sappemeer17:04
  6. Zuidbroek17:09
  7. Veendam17:17

Next service: Sunday 16:48 from Groningen · Sun 22 Nov

Next departure 16:48 Sunday · Groningen
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 1 full · 3 partial · 1 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 1 full · 4 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Veendam, 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

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

  • Early 0% · 0
  • On time 100% · 5
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 5 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
16:48on time on time
16:50— —
16:59— —
17:01— —
17:04— —
17:09— —
17:17— —

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
Sun 15 NovZuidbroek 17:23Partial coverage0 min—
Sun 8 NovZuidbroek 17:24Partial coverage0 min—
Sun 1 NovZuidbroek 17:24Partial coverage0 min—
Sun 25 OctZuidbroek 17:25No data—
Sun 18 OctZuidbroek 17:240 min—
Sun 11 OctZuidbroek 17:25Partial coverage+1 min—
Sun 4 OctZuidbroek 17:23No data—
Sun 27 SeptZuidbroek 17:23No data—
Sun 20 SeptZuidbroek 17:24No data—
Sun 13 SeptZuidbroek 17:25No data—
Sun 6 SeptZuidbroek 17:24No data—
Sun 30 AugZuidbroek 17:23No data—
Sun 23 AugZuidbroek 17:23No data—