Train Arriva 37858 Delfzijl – Veendam

Delfzijl 15:48 → Veendam 16: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 17:04 +1 min

  1. Delfzijl15:48
  2. Appingedam15:54
  3. Bedum16:11
  4. Groningen Noord16:20
  5. Groningen Europapark16:31
  6. Zuidbroek16:50
  7. Veendam16:57

Next service: Monday 15:48 from Delfzijl · Mon 9 Nov

Next departure 15:48 Monday · Delfzijl
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 15 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 63 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 14 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
15:48on time on time
15:50— —
15:54— —
16:00— —
16:04— —
16:11— —
16:15— —
16:20 / 16:21— —
16:26 / 16:29— —
16:31— —
16:40— —
16:42— —
16:45— —
16:50— —
16: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
Sat 7 NovZuidbroek 17:04Partial coverage+1 min+1 min
Fri 6 NovZuidbroek 17:04No data—
Thu 5 NovZuidbroek 17:04No data—
Wed 4 NovZuidbroek 17:04Partial coverage0 min—
Tue 3 NovZuidbroek 17:05No data—
Mon 2 NovZuidbroek 17:04No data—
Sat 31 OctZuidbroek 17:04Partial coverage0 min—
Fri 30 OctZuidbroek 17:05No data—
Thu 29 OctZuidbroek 17:04No data—
Wed 28 OctZuidbroek 17:08Partial coverage0 min—
Tue 27 OctHoogezand-Sappemeer 16:59No data—
Mon 26 OctZuidbroek 17:04Partial coverage0 min—
Sat 24 OctZuidbroek 17:04Partial coverage0 min—
Fri 23 OctZuidbroek 17:06No data—
Thu 22 OctZuidbroek 17:10No data—
Wed 21 OctZuidbroek 17:05No data—
Tue 20 OctZuidbroek 17:05Partial coverage0 min—
Mon 19 OctZuidbroek 17:04Partial coverage0 min—
Sat 17 OctZuidbroek 17:04No data—
Fri 16 OctZuidbroek 17:05No data—
Thu 15 OctZuidbroek 17:04No data—
Wed 14 OctZuidbroek 17:05No data—
Tue 13 OctZuidbroek 17:04No data—
Mon 12 OctZuidbroek 17:05Partial coverage0 min—
Sat 10 OctZuidbroek 17:04Partial coverage0 min—
Fri 9 OctZuidbroek 17:04Partial coverage0 min—
Thu 8 OctZuidbroek 17:04Partial coverage0 min—
Wed 7 OctZuidbroek 17:04Partial coverage+1 min+1 min
Tue 6 OctZuidbroek 17:04No data—
Mon 5 OctZuidbroek 17:05Partial coverage0 min—