Train Arriva 37812 Groningen – Veendam

Groningen 05:01 → Veendam 05:30 Mon, Tue, Wed, Thu, Fri 0 h 29 min · 7 stops Arriva

It does not run today

Last recorded run: Friday 6 November No data

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

Next departure 05:01 Monday · Groningen
On-time · 30 days
93%
14/15 runs under 3 min
RT coverage: 14 full · 1 partial · 6 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 47 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

Worst days

  • Thu 5 Nov Max en route +5 min · last fix heading to Zuidbroek +5 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 16
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=3
  • 75% T n=4
  • 100% F n=2
  • — S n=0
  • — S n=0

Stops and timetable

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

Last 90 days, 17 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:01on time on time
05:04≈ on time ≈ on time
05:12≈ on time ≈ on time
05:15≈ on time ≈ +1 min
05:18≈ on time ≈ +1 min
05:23≈ on time ≈ +1 min
05:30on time +1 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
Fri 6 NovZuidbroek 05:34No data—
Thu 5 NovZuidbroek 05:42Partial coverage+5 min+5 min
Wed 4 NovZuidbroek 05:34No data—
Tue 3 NovZuidbroek 05:34+2 min+2 min
Mon 2 NovZuidbroek 05:340 min—
Fri 30 OctZuidbroek 05:34No data—
Thu 29 OctZuidbroek 05:360 min—
Wed 28 OctZuidbroek 05:340 min—
Tue 27 OctZuidbroek 05:340 min—
Mon 26 OctZuidbroek 05:340 min—
Fri 23 OctZuidbroek 05:340 min—
Thu 22 OctZuidbroek 05:370 min—
Wed 21 OctZuidbroek 05:34No data—
Tue 20 OctZuidbroek 05:340 min—
Mon 19 OctZuidbroek 05:340 min—
Fri 16 OctZuidbroek 05:32No data—
Thu 15 OctZuidbroek 05:360 min—
Wed 14 OctZuidbroek 05:340 min—
Tue 13 OctZuidbroek 05:340 min—
Mon 12 OctZuidbroek 05:34No data—
Fri 9 OctZuidbroek 05:340 min—
Thu 8 OctZuidbroek 05:38No data—
Wed 7 OctZuidbroek 05:34+1 min+1 min
Tue 6 OctZuidbroek 05:34+1 min+1 min
Mon 5 OctZuidbroek 05:35No data—
Fri 2 OctZuidbroek 05:34No data—
Thu 1 OctZuidbroek 05:37No data—
Wed 30 SeptZuidbroek 05:34No data—
Tue 29 SeptZuidbroek 05:34No data—
Mon 28 SeptZuidbroek 05:34No data—