Train Arriva 37820 Delfzijl – Veendam

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

✓ Today’s run finished

Today, last fix heading to Zuidbroek at 07:34 No data

  1. Delfzijl06:18
  2. Appingedam06:24
  3. Bedum06:41
  4. Groningen Noord06:50
  5. Groningen Europapark07:01
  6. Zuidbroek07:20
  7. Veendam07:27

Next service: tomorrow 06:18 from Delfzijl · Fri 6 Nov

Next departure 06:18 tomorrow · Delfzijl
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 4 full · 19 partial · 3 no data
On-time · 90 days
96%
23/24 runs under 3 min
RT coverage: 4 full · 20 partial · 52 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

Worst days

  • Fri 23 Oct Max en route +6 min · last fix heading to Zuidbroek +6 min

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 96% · 23
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=5
  • 100% W n=5
  • 100% T n=4
  • 75% F n=4
  • 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, 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
06:18on time on time
06:20— —
06:24— —
06:30— —
06:34— —
06:41— —
06:45— —
06:50 / 06:51— —
06:56 / 06:59— —
07:01— —
07:10— —
07:12— —
07:15— —
07:20— —
07: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
Thu 5 NovZuidbroek 07:34No data—
Wed 4 NovZuidbroek 07:34Partial coverage0 min—
Tue 3 NovZuidbroek 07:34Partial coverage0 min—
Mon 2 NovZuidbroek 07:34No data—
Sat 31 OctZuidbroek 07:340 min—
Fri 30 OctZuidbroek 07:34Partial coverage0 min—
Thu 29 OctZuidbroek 07:35Partial coverage+1 min—
Wed 28 OctZuidbroek 07:34Partial coverage0 min—
Tue 27 OctHoogezand-Sappemeer 07:38Partial coverage0 min—
Mon 26 OctZuidbroek 07:35Partial coverage0 min—
Sat 24 OctZuidbroek 07:35+1 min—
Fri 23 OctZuidbroek 07:41Partial coverage+6 min+6 min
Thu 22 OctZuidbroek 07:35Partial coverage0 min—
Wed 21 OctZuidbroek 07:35Partial coverage0 min—
Tue 20 OctZuidbroek 07:35Partial coverage0 min—
Mon 19 OctZuidbroek 07:35Partial coverage0 min—
Sat 17 OctZuidbroek 07:34No data—
Fri 16 OctZuidbroek 07:340 min—
Thu 15 OctZuidbroek 07:35Partial coverage0 min—
Wed 14 OctZuidbroek 07:34Partial coverage0 min—
Tue 13 OctZuidbroek 07:37Partial coverage0 min—
Mon 12 OctZuidbroek 07:34Partial coverage0 min—
Sat 10 OctZuidbroek 07:350 min—
Fri 9 OctZuidbroek 07:35Partial coverage0 min—
Thu 8 OctZuidbroek 07:35Partial coverage0 min—
Wed 7 OctZuidbroek 07:35Partial coverage0 min—
Tue 6 OctZuidbroek 07:35Partial coverage+1 min—
Mon 5 OctZuidbroek 07:39No data—
Sat 3 OctZuidbroek 07:35No data—
Fri 2 OctZuidbroek 07:35No data—