Train Arriva 37868 Delfzijl – Veendam

Delfzijl 18:18 → Veendam 19:27 Mon, Tue, Wed, Thu, Fri, Sat 1 h 09 min · 15 stops Arriva

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 18:18 from Delfzijl · Mon 16 Nov

Next departure 18:18 today · Delfzijl
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 0 full · 10 partial · 4 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 30 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: +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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • — W n=0
  • 100% T n=1
  • 100% F n=4
  • 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, 13 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
18:18on time on time
18:20— —
18:24— —
18:30— —
18:34— —
18:41— —
18:45— —
18:50 / 18:51— —
18:56 / 18:59— —
19:01— —
19:10— —
19:12— —
19:15— —
19:20— —
19:27— —

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 14 NovZuidbroek 19:34Partial coverage0 min—
Fri 13 NovGroningen Noord 19:04Partial coverage+1 min—
Thu 12 NovDelfzijl West 18:34Partial coverage0 min—
Tue 10 NovDelfzijl West 18:34Partial coverage0 min—
Sat 7 NovZuidbroek 19:34Partial coverage0 min—
Fri 6 NovSauwerd 18:59Partial coverage0 min—
Sat 31 OctZuidbroek 19:36Partial coverage+2 min+2 min
Fri 30 OctGroningen Noord 19:05No data—
Sat 24 OctZuidbroek 19:35No data—
Fri 23 OctZuidbroek 19:34Partial coverage0 min—
Thu 22 OctAppingedam 19:32No data—
Wed 21 OctStedum 19:33No data—
Tue 20 OctSauwerd 18:50Partial coverage0 min—
Mon 19 OctBedum 18:55Partial coverage0 min—
Sat 17 OctZuidbroek 19:34No data—
Fri 16 OctZuidbroek 19:34No data—
Thu 15 OctLoppersum 18:44No data—
Wed 14 OctZuidbroek 19:34No data—
Tue 13 OctStedum 18:48No data—
Mon 12 OctSauwerd 18:59Partial coverage0 min—
Sat 10 OctZuidbroek 19:35Partial coverage0 min—
Fri 9 OctStedum 18:48Partial coverage0 min—
Sat 3 OctZuidbroek 19:36No data—
Fri 2 OctSauwerd 18:59No data—
Sat 26 SeptZuidbroek 19:35No data—
Fri 25 SeptStedum 18:48No data—
Sat 19 SeptZuidbroek 19:35No data—
Fri 18 SeptSauwerd 18:59No data—
Sat 12 SeptZuidbroek 19:34No data—
Fri 11 SeptSauwerd 18:59No data—