Train Arriva 37862 Delfzijl – Veendam

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

It has not run yet today

Last recorded run: Thursday 5 November No data

Next service: today 16:48 from Delfzijl · Fri 6 Nov

Next departure 16:48 today · Delfzijl
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 0 full · 12 partial · 13 no data
On-time · 90 days
93%
14/15 runs under 3 min
RT coverage: 0 full · 15 partial · 60 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 31 Oct Max en route +6 min · last fix heading to Zuidbroek +6 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=5
  • 100% T n=3
  • 100% W n=2
  • 100% T n=1
  • 100% F n=1
  • 67% 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
16:48on time on time
16:50— —
16:54— —
17:00— —
17:04— —
17:11— —
17:15— —
17:20 / 17:21— —
17:26 / 17:29— —
17:31— —
17:40— —
17:42— —
17:45— —
17:50— —
17: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
Thu 5 NovZuidbroek 18:04No data—
Wed 4 NovZuidbroek 18:04No data—
Tue 3 NovZuidbroek 18:04Partial coverage0 min—
Mon 2 NovZuidbroek 18:04Partial coverage0 min—
Sat 31 OctZuidbroek 18:10Partial coverage+6 min+6 min
Fri 30 OctZuidbroek 18:04No data—
Thu 29 OctZuidbroek 18:04No data—
Wed 28 OctZuidbroek 18:04Partial coverage0 min—
Tue 27 OctZuidbroek 18:04No data—
Mon 26 OctZuidbroek 18:04Partial coverage+1 min—
Sat 24 OctZuidbroek 18:05Partial coverage0 min—
Fri 23 OctZuidbroek 18:04No data—
Thu 22 OctZuidbroek 18:04No data—
Wed 21 OctZuidbroek 18:04No data—
Tue 20 OctZuidbroek 18:04Partial coverage0 min—
Mon 19 OctZuidbroek 18:04Partial coverage0 min—
Sat 17 OctZuidbroek 18:04No data—
Fri 16 OctZuidbroek 18:05No data—
Thu 15 OctZuidbroek 18:04No data—
Wed 14 OctZuidbroek 18:04No data—
Tue 13 OctZuidbroek 18:04No data—
Mon 12 OctZuidbroek 18:04Partial coverage0 min—
Sat 10 OctZuidbroek 18:05Partial coverage0 min—
Fri 9 OctZuidbroek 18:04Partial coverage0 min—
Thu 8 OctZuidbroek 18:05Partial coverage0 min—
Wed 7 OctZuidbroek 18:04Partial coverage0 min—
Tue 6 OctZuidbroek 18:04Partial coverage0 min—
Mon 5 OctZuidbroek 18:04Partial coverage0 min—
Sat 3 OctZuidbroek 18:04No data—
Fri 2 OctZuidbroek 18:04No data—