Train Arriva 37866 Delfzijl – Veendam

Delfzijl 17:48 → Veendam 18: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 19:04 0 min

  1. Delfzijl17:48
  2. Appingedam17:54
  3. Bedum18:11
  4. Groningen Noord18:20
  5. Groningen Europapark18:31
  6. Zuidbroek18:50
  7. Veendam18:57

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

Next departure 17:48 Monday · Delfzijl
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 0 full · 14 partial · 12 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 2 full · 16 partial · 59 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 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=3
  • 100% W n=2
  • 100% T n=2
  • 100% F n=3
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 18 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
17:48on time on time
17:50— —
17:54— —
18:00— —
18:04— —
18:11— —
18:15— —
18:20 / 18:21— —
18:26 / 18:29— —
18:31— —
18:40— —
18:42— —
18:45— —
18:50— —
18: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 19:04Partial coverage0 min—
Fri 6 NovHoogezand-Sappemeer 18:59Partial coverage+1 min+1 min
Thu 5 NovBedum 18:24No data—
Wed 4 NovSauwerd 18:29No data—
Tue 3 NovAppingedam 18:59Partial coverage0 min—
Mon 2 NovAppingedam 18:58Partial coverage0 min—
Sat 31 OctZuidbroek 19:04Partial coverage0 min—
Fri 30 OctZuidbroek 19:04No data—
Thu 29 OctAppingedam 19:01Partial coverage+2 min+2 min
Wed 28 OctAppingedam 18:08Partial coverage0 min—
Tue 27 OctStedum 18:18No data—
Mon 26 OctStedum 18:18Partial coverage0 min—
Sat 24 OctZuidbroek 19:04No data—
Fri 23 OctZuidbroek 19:04Partial coverage0 min—
Thu 22 OctHoogezand-Sappemeer 19:01No data—
Wed 21 OctKropswolde 18:54No data—
Tue 20 OctHoogezand-Sappemeer 19:02Partial coverage0 min—
Mon 19 OctMartenshoek 19:01Partial coverage0 min—
Sat 17 OctZuidbroek 19:05No data—
Fri 16 OctZuidbroek 19:04No data—
Thu 15 OctGroningen 18:43No data—
Wed 14 OctZuidbroek 19:04No data—
Tue 13 OctKropswolde 18:50No data—
Mon 12 OctHoogezand-Sappemeer 18:59Partial coverage0 min—
Sat 10 OctZuidbroek 19:04Partial coverage0 min—
Fri 9 OctGroningen Europapark 19:00Partial coverage0 min—
Thu 8 OctLoppersum 18:140 min—
Wed 7 OctStedum 18:18Partial coverage0 min—
Tue 6 OctAppingedam 19:03+2 min+2 min
Mon 5 OctBedum 18:25Partial coverage0 min—