Train Arriva 37850 Delfzijl – Veendam

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

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 13:48 from Delfzijl · Sat 7 Nov

Next departure 13:48 today · Delfzijl
On-time · 30 days
100%
9/9 runs under 3 min
RT coverage: 0 full · 9 partial · 16 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 0 full · 13 partial · 63 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

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • — F n=0
  • 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, 13 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
13:48on time on time
13:50— —
13:54— —
14:00— —
14:04— —
14:11— —
14:15— —
14:20 / 14:21— —
14:26 / 14:29— —
14:31— —
14:40— —
14:42— —
14:45— —
14:50— —
14: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
Fri 6 NovZuidbroek 15:04No data—
Thu 5 NovZuidbroek 15:04No data—
Wed 4 NovZuidbroek 15:04Partial coverage0 min—
Tue 3 NovZuidbroek 15:04No data—
Mon 2 NovZuidbroek 15:04No data—
Sat 31 OctZuidbroek 15:04Partial coverage0 min—
Fri 30 OctZuidbroek 15:05No data—
Thu 29 OctZuidbroek 15:04No data—
Wed 28 OctZuidbroek 15:05Partial coverage0 min—
Tue 27 OctZuidbroek 15:06Partial coverage0 min—
Mon 26 OctZuidbroek 15:06Partial coverage0 min—
Sat 24 OctZuidbroek 15:04Partial coverage0 min—
Fri 23 OctZuidbroek 15:04No data—
Thu 22 OctZuidbroek 15:07No data—
Wed 21 OctZuidbroek 15:29No data—
Tue 20 OctZuidbroek 15:04Partial coverage0 min—
Mon 19 OctZuidbroek 15:04Partial coverage0 min—
Sat 17 OctZuidbroek 15:04No data—
Fri 16 OctZuidbroek 15:04No data—
Thu 15 OctZuidbroek 15:05No data—
Wed 14 OctHoogezand-Sappemeer 15:11No data—
Tue 13 OctZuidbroek 15:04No data—
Mon 12 OctZuidbroek 15:05No data—
Sat 10 OctZuidbroek 15:04Partial coverage0 min—
Fri 9 OctZuidbroek 15:04No data—
Thu 8 OctZuidbroek 15:05Partial coverage+1 min—
Wed 7 OctZuidbroek 15:05Partial coverage0 min—
Tue 6 OctZuidbroek 15:04Partial coverage0 min—
Mon 5 OctZuidbroek 15:05Partial coverage0 min—
Sat 3 OctZuidbroek 15:04No data—