Train Arriva 37830 Delfzijl – Veendam

Delfzijl 08:48 → Veendam 09:57 Mon, Tue, Wed, Thu, Fri, Sat 1 h 09 min · 15 stops Arriva

✓ Today’s run finished

Today, last fix heading to Zuidbroek at 10:04 0 min

  1. Delfzijl08:48
  2. Appingedam08:54
  3. Bedum09:11
  4. Groningen Noord09:20
  5. Groningen Europapark09:31
  6. Zuidbroek09:50
  7. Veendam09:57

Next service: tomorrow 08:48 from Delfzijl · Tue 17 Nov

Next departure 08:48 tomorrow · Delfzijl
On-time · 30 days
100%
18/18 runs under 3 min
RT coverage: 0 full · 18 partial · 7 no data
On-time · 90 days
100%
24/24 runs under 3 min
RT coverage: 1 full · 23 partial · 52 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 24 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
08:48on time on time
08:50— —
08:54— —
09:00— —
09:04— —
09:11— —
09:15— —
09:20 / 09:21— —
09:26 / 09:29— —
09:31— —
09:40— —
09:42— —
09:45— —
09:50— —
09:57— —

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 16 NovZuidbroek 10:04Partial coverage0 min—
Sat 14 NovZuidbroek 10:04Partial coverage0 min—
Fri 13 NovZuidbroek 10:04Partial coverage0 min—
Thu 12 NovZuidbroek 10:04Partial coverage0 min—
Wed 11 NovZuidbroek 10:04Partial coverage0 min—
Tue 10 NovZuidbroek 10:04Partial coverage0 min—
Mon 9 NovZuidbroek 10:04Partial coverage0 min—
Sat 7 NovZuidbroek 10:04Partial coverage0 min—
Fri 6 NovZuidbroek 10:04No data—
Thu 5 NovZuidbroek 10:04No data—
Wed 4 NovZuidbroek 10:04Partial coverage0 min—
Tue 3 NovZuidbroek 10:04Partial coverage0 min—
Mon 2 NovZuidbroek 10:04Partial coverage0 min—
Sat 31 OctZuidbroek 10:04No data—
Fri 30 OctZuidbroek 10:04No data—
Thu 29 OctZuidbroek 10:04Partial coverage0 min—
Wed 28 OctZuidbroek 10:05Partial coverage0 min—
Tue 27 OctZuidbroek 10:05Partial coverage0 min—
Mon 26 OctZuidbroek 10:04Partial coverage0 min—
Sat 24 OctZuidbroek 10:06Partial coverage+2 min+2 min
Fri 23 OctZuidbroek 10:07No data—
Thu 22 OctZuidbroek 10:05No data—
Wed 21 OctZuidbroek 10:08No data—
Tue 20 OctZuidbroek 10:04Partial coverage0 min—
Mon 19 OctZuidbroek 10:04Partial coverage0 min—
Sat 17 OctZuidbroek 10:040 min—
Fri 16 OctZuidbroek 10:05No data—
Thu 15 OctZuidbroek 10:04No data—
Wed 14 OctZuidbroek 10:04No data—
Tue 13 OctZuidbroek 10:04No data—