Train Arriva 37824 Delfzijl – Veendam

Delfzijl 07:18 → Veendam 08: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 08:34 No data

  1. Delfzijl07:18
  2. Appingedam07:24
  3. Bedum07:41
  4. Groningen Noord07:50
  5. Groningen Europapark08:01
  6. Zuidbroek08:20
  7. Veendam08:27

Next service: tomorrow 07:18 from Delfzijl · Sat 7 Nov

Next departure 07:18 tomorrow · Delfzijl
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 3 full · 10 partial · 13 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 3 full · 12 partial · 61 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
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

  • Tue 6 Oct Max en route +3 min · last fix heading to Zuidbroek +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 14
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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