Train Arriva 37859 Veendam – Delfzijl

Veendam 17:32 → Delfzijl 18:43 Mon, Tue, Wed, Thu, Fri, Sat 1 h 11 min · 15 stops Arriva

It has not run yet today

Last recorded run: Wednesday 4 November 0 min

Next service: today 17:32 from Veendam · Thu 5 Nov

Next departure 17:32 today · Veendam
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 2 full · 12 partial · 11 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 2 full · 14 partial · 59 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 Delfzijl, 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=2
  • 100% W n=3
  • 100% T n=2
  • 100% F n=2
  • 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, 16 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
17:32on time on time
17:38— —
17:43— —
17:46— —
17:49— —
17:57— —
18:00 / 18:04— —
18:08 / 18:10— —
18:15— —
18:20— —
18:26— —
18:30— —
18:36 / 18:37— —
18:41— —
18:43— —

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
Wed 4 NovSauwerd 18:29Partial coverage0 min—
Tue 3 NovGroningen Noord 18:24No data—
Mon 2 NovGroningen Noord 18:24No data—
Sat 31 OctDelfzijl West 18:56Partial coverage0 min—
Fri 30 OctDelfzijl West 18:55No data—
Thu 29 OctGroningen Europapark 18:11No data—
Wed 28 OctZuidbroek 18:460 min—
Tue 27 OctZuidbroek 18:49No data—
Mon 26 OctGroningen 18:18Partial coverage0 min—
Sat 24 OctDelfzijl West 18:55Partial coverage0 min—
Fri 23 OctDelfzijl West 18:53Partial coverage+1 min+1 min
Thu 22 OctDelfzijl West 18:55No data—
Wed 21 OctAppingedam 18:51No data—
Tue 20 OctDelfzijl West 18:50Partial coverage0 min—
Mon 19 OctDelfzijl West 18:55Partial coverage0 min—
Sat 17 OctGroningen Europapark 18:11No data—
Fri 16 OctGroningen Europapark 18:13No data—
Thu 15 OctLoppersum 18:440 min—
Wed 14 OctDelfzijl West 18:55No data—
Tue 13 OctAppingedam 18:50No data—
Mon 12 OctDelfzijl West 18:55Partial coverage0 min—
Sat 10 OctDelfzijl West 18:55Partial coverage0 min—
Fri 9 OctLoppersum 18:44Partial coverage0 min—
Thu 8 OctGroningen Europapark 18:12Partial coverage0 min—
Wed 7 OctGroningen 18:18Partial coverage0 min—
Tue 6 OctGroningen 18:18Partial coverage0 min—
Mon 5 OctGroningen Noord 18:24Partial coverage0 min—
Sat 3 OctDelfzijl West 18:56No data—
Fri 2 OctDelfzijl West 18:55No data—
Thu 1 OctGroningen 18:18No data—