Train Arriva 37863 Veendam – Delfzijl

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

It has not run yet today

Last recorded run: Friday 6 November 0 min

Next service: today 18:32 from Veendam · Sat 7 Nov

Next departure 18:32 today · Veendam
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 8 no data
On-time · 90 days
100%
8/8 runs under 3 min
RT coverage: 0 full · 8 partial · 35 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 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

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

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

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • — W n=0
  • — T n=0
  • 100% F n=3
  • 100% S n=2
  • — S n=0

Stops and timetable

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

Last 90 days, 8 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
18:32on time on time
18:38— —
18:43— —
18:46— —
18:49— —
18:57— —
19:00 / 19:04— —
19:08 / 19:10— —
19:15— —
19:20— —
19:26— —
19:30— —
19:36 / 19:37— —
19:41— —
19: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
Fri 6 NovMartenshoek 18:59Partial coverage0 min—
Sat 31 OctDelfzijl West 19:56Partial coverage+1 min—
Fri 30 OctKropswolde 19:03No data—
Sat 24 OctDelfzijl West 19:56No data—
Fri 23 OctStedum 19:40Partial coverage+1 min—
Thu 22 OctHoogezand-Sappemeer 18:57No data—
Wed 21 OctZuidbroek 18:52No data—
Tue 20 OctMartenshoek 18:50Partial coverage0 min—
Mon 19 OctHoogezand-Sappemeer 18:57Partial coverage0 min—
Sat 17 OctGroningen Europapark 19:11No data—
Fri 16 OctGroningen Europapark 19:11No data—
Wed 14 OctDelfzijl West 19:55No data—
Tue 13 OctZuidbroek 18:50No data—
Mon 12 OctHoogezand-Sappemeer 18:57Partial coverage0 min—
Sat 10 OctDelfzijl West 19:55Partial coverage0 min—
Fri 9 OctVeendam 18:46Partial coverage0 min—
Sat 3 OctDelfzijl West 19:56No data—
Fri 2 OctMartenshoek 19:00No data—
Sat 26 SeptGroningen Europapark 19:11No data—
Fri 25 SeptVeendam 18:46No data—
Sat 19 SeptDelfzijl West 19:55No data—
Fri 18 SeptMartenshoek 19:00No data—
Sat 12 SeptDelfzijl West 20:02No data—
Fri 11 SeptKropswolde 19:03No data—
Sat 5 SeptDelfzijl West 19:55No data—
Fri 4 SeptKropswolde 19:03No data—
Sat 29 AugDelfzijl West 19:55No data—
Fri 28 AugLoppersum 19:44No data—
Thu 27 AugMartenshoek 19:00No data—
Wed 26 AugGroningen 19:18No data—