Train Arriva 37856 Delfzijl – Veendam

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

It has not run yet today

Last recorded run: Monday 16 November +1 min

Next service: today 15:18 from Delfzijl · Tue 17 Nov

Next departure 15:18 today · Delfzijl
On-time · 30 days
100%
16/16 runs under 3 min
RT coverage: 1 full · 15 partial · 9 no data
On-time · 90 days
100%
23/23 runs under 3 min
RT coverage: 1 full · 22 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: +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

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

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

On-time by weekday

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