Train Arriva 37826 Delfzijl – Veendam

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 07:48 from Delfzijl · Tue 17 Nov

Next departure 07:48 today · Delfzijl
On-time · 30 days
95%
19/20 runs under 3 min
RT coverage: 0 full · 20 partial · 5 no data
On-time · 90 days
92%
23/25 runs under 3 min
RT coverage: 0 full · 25 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 12 Nov Max en route +5 min · last fix heading to Zuidbroek +5 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Zuidbroek +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 23
  • 3–10 min 8% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 80% T n=5
  • 100% W n=4
  • 67% T n=3
  • 100% F n=3
  • 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, 25 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
07:48on time on time
07:50— —
07:54— —
08:00— —
08:04— —
08:11— —
08:15— —
08:20 / 08:21— —
08:26 / 08:29— —
08:31— —
08:40— —
08:42— —
08:45— —
08:50— —
08: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 09:04Partial coverage+1 min+1 min
Sat 14 NovZuidbroek 09:04Partial coverage0 min—
Fri 13 NovZuidbroek 09:04Partial coverage+1 min+1 min
Thu 12 NovZuidbroek 09:09Partial coverage+5 min+5 min
Wed 11 NovZuidbroek 09:07Partial coverage+3 min+3 min
Tue 10 NovZuidbroek 09:07Partial coverage+3 min+3 min
Mon 9 NovZuidbroek 09:04Partial coverage0 min—
Sat 7 NovZuidbroek 09:04Partial coverage0 min—
Fri 6 NovZuidbroek 09:04No data—
Thu 5 NovZuidbroek 09:04No data—
Wed 4 NovZuidbroek 09:04Partial coverage0 min—
Tue 3 NovZuidbroek 09:04Partial coverage0 min—
Mon 2 NovZuidbroek 09:07Partial coverage0 min—
Sat 31 OctZuidbroek 09:04Partial coverage0 min—
Fri 30 OctZuidbroek 09:06No data—
Thu 29 OctZuidbroek 09:04Partial coverage0 min—
Wed 28 OctZuidbroek 09:05Partial coverage0 min—
Tue 27 OctZuidbroek 09:05Partial coverage0 min—
Mon 26 OctZuidbroek 09:06Partial coverage0 min—
Sat 24 OctZuidbroek 09:04Partial coverage0 min—
Fri 23 OctGroningen 09:42Partial coverage0 min—
Thu 22 OctZuidbroek 09:07No data—
Wed 21 OctZuidbroek 09:05No data—
Tue 20 OctZuidbroek 09:07Partial coverage0 min—
Mon 19 OctZuidbroek 09:04Partial coverage0 min—
Sat 17 OctZuidbroek 09:04No data—
Fri 16 OctZuidbroek 09:04No data—
Thu 15 OctZuidbroek 09:05No data—
Wed 14 OctZuidbroek 09:06No data—
Tue 13 OctZuidbroek 09:04No data—