Train Arriva 37836 Delfzijl – Veendam

Delfzijl 10:18 → Veendam 11: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 11:34 0 min

  1. Delfzijl10:18
  2. Appingedam10:24
  3. Bedum10:41
  4. Groningen Noord10:50
  5. Groningen Europapark11:01
  6. Zuidbroek11:20
  7. Veendam11:27

Next service: tomorrow 10:18 from Delfzijl · Tue 17 Nov

Next departure 10:18 tomorrow · Delfzijl
On-time · 30 days
95%
18/19 runs under 3 min
RT coverage: 0 full · 19 partial · 6 no data
On-time · 90 days
91%
21/23 runs under 3 min
RT coverage: 0 full · 23 partial · 53 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

Worst days

  • Sat 14 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

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

  • Early 0% · 0
  • On time 91% · 21
  • 3–10 min 9% · 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
  • 100% T n=3
  • 100% F n=2
  • 75% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 23 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
10:18on time on time
10:20— —
10:24— —
10:30— —
10:34— —
10:41— —
10:45— —
10:50 / 10:51— —
10:56 / 10:59— —
11:01— —
11:10— —
11:12— —
11:15— —
11:20— —
11: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
Mon 16 NovZuidbroek 11:34Partial coverage0 min—
Sat 14 NovZuidbroek 11:39Partial coverage+5 min+5 min
Fri 13 NovZuidbroek 11:34Partial coverage0 min—
Thu 12 NovZuidbroek 11:34Partial coverage0 min—
Wed 11 NovZuidbroek 11:34Partial coverage+1 min+1 min
Tue 10 NovZuidbroek 11:34Partial coverage0 min—
Mon 9 NovZuidbroek 11:34Partial coverage0 min—
Sat 7 NovZuidbroek 11:34Partial coverage0 min—
Fri 6 NovZuidbroek 11:34No data—
Thu 5 NovZuidbroek 11:34No data—
Wed 4 NovZuidbroek 11:34Partial coverage0 min—
Tue 3 NovZuidbroek 11:35Partial coverage0 min—
Mon 2 NovZuidbroek 11:34Partial coverage0 min—
Sat 31 OctZuidbroek 11:36Partial coverage+1 min+1 min
Fri 30 OctZuidbroek 11:35No data—
Thu 29 OctZuidbroek 11:34Partial coverage0 min—
Wed 28 OctZuidbroek 11:34Partial coverage0 min—
Tue 27 OctZuidbroek 11:34Partial coverage0 min—
Mon 26 OctZuidbroek 11:34Partial coverage0 min—
Sat 24 OctZuidbroek 11:34Partial coverage0 min—
Fri 23 OctZuidbroek 11:36No data—
Thu 22 OctZuidbroek 11:34No data—
Wed 21 OctZuidbroek 11:34No data—
Tue 20 OctZuidbroek 11:35Partial coverage0 min—
Mon 19 OctZuidbroek 11:34Partial coverage0 min—
Sat 17 OctZuidbroek 11:34No data—
Fri 16 OctZuidbroek 11:34No data—
Thu 15 OctZuidbroek 11:34No data—
Wed 14 OctZuidbroek 11:34No data—
Tue 13 OctZuidbroek 11:34No data—