Train Arriva 37816 Groningen – Veendam

Groningen 05:59 → Veendam 06:27 Mon, Tue, Wed, Thu, Fri, Sat 0 h 28 min · 7 stops Arriva

✓ Today’s run finished

Today, last fix heading to Zuidbroek at 06:37 +3 min

  1. Groningen05:59
  2. Groningen Europapark06:01
  3. Kropswolde06:10
  4. Martenshoek06:12
  5. Hoogezand-Sappemeer06:15
  6. Zuidbroek06:20
  7. Veendam06:27

Next service: Monday 05:59 from Groningen · Mon 9 Nov

Next departure 05:59 Monday · Groningen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 5 no data
On-time · 90 days
100%
22/22 runs under 3 min
RT coverage: 19 full · 3 partial · 55 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

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

  • Early 0% · 0
  • On time 100% · 22
  • 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=4
  • 100% W n=5
  • 100% T n=3
  • 100% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 22 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
05:59on time on time
06:01≈ on time ≈ on time
06:10≈ on time ≈ +1 min
06:12≈ on time ≈ +1 min
06:15≈ on time ≈ +1 min
06:20≈ on time ≈ +1 min
06:27+1 min +2 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
Sat 7 NovZuidbroek 06:37Partial coverage+3 min+3 min
Fri 6 NovZuidbroek 06:34No data—
Thu 5 NovZuidbroek 06:340 min—
Wed 4 NovZuidbroek 06:340 min—
Tue 3 NovZuidbroek 06:34+1 min—
Mon 2 NovZuidbroek 06:34No data—
Sat 31 OctZuidbroek 06:36Partial coverage+2 min+2 min
Fri 30 OctZuidbroek 06:35+1 min+1 min
Thu 29 OctZuidbroek 06:35No data—
Wed 28 OctZuidbroek 06:36+1 min+1 min
Tue 27 OctZuidbroek 06:36+2 min+2 min
Mon 26 OctZuidbroek 06:35+1 min—
Sat 24 OctZuidbroek 06:34No data—
Fri 23 OctZuidbroek 06:37+3 min+3 min
Thu 22 OctZuidbroek 06:35+1 min—
Wed 21 OctZuidbroek 06:36+1 min+1 min
Tue 20 OctZuidbroek 06:36+1 min+1 min
Mon 19 OctZuidbroek 06:350 min—
Sat 17 OctZuidbroek 06:340 min—
Fri 16 OctZuidbroek 06:34No data—
Thu 15 OctZuidbroek 06:35+1 min—
Wed 14 OctZuidbroek 06:350 min—
Tue 13 OctZuidbroek 06:36+2 min+2 min
Mon 12 OctZuidbroek 06:340 min—
Sat 10 OctZuidbroek 06:36Partial coverage+2 min+2 min
Fri 9 OctZuidbroek 06:340 min—
Thu 8 OctZuidbroek 06:35No data—
Wed 7 OctZuidbroek 06:35+1 min—
Tue 6 OctZuidbroek 06:34No data—
Mon 5 OctZuidbroek 06:37No data—