Train Arriva 37525 Veendam – Eemshaven

Veendam 08:44 → Eemshaven 10:11 Sun 1 h 27 min · 17 stops Arriva

✓ Today’s run finished

Today, last fix heading to Roodeschool at 10:19 0 min

  1. Veendam08:44
  2. Martenshoek08:59
  3. Groningen Europapark09:09
  4. Sauwerd09:30
  5. Warffum09:45
  6. Roodeschool10:03
  7. Eemshaven10:11

Next service: Sunday 08:44 from Veendam · Sun 22 Nov

Next departure 08:44 Sunday · Veendam
On-time · 30 days
100%
4/4 runs under 3 min
RT coverage: 3 full · 1 partial · 1 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 4 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
P90
+1min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Eemshaven, 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

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

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

On-time by weekday

  • — M n=0
  • — T n=0
  • — W n=0
  • — T n=0
  • — F n=0
  • — S n=0
  • 100% S n=5

Stops and timetable

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

Last 90 days, 5 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
08:44on time on time
08:50— —
08:56— —
08:59— —
09:01— —
09:09— —
09:13 / 09:19— —
09:24— —
09:30— —
09:35— —
09:39 / 09:40— —
09:45— —
09:49 / 09:50— —
09:55— —
09:59 / 10:00— —
10:03 / 10:04— —
10:11— —

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
Sun 15 NovRoodeschool 10:19Partial coverage0 min+1 min
Sun 8 NovRoodeschool 10:180 min—
Sun 1 NovRoodeschool 10:190 min—
Sun 25 OctRoodeschool 10:19No data—
Sun 18 OctGroningen Europapark 09:230 min—
Sun 11 OctRoodeschool 10:19+1 min+1 min
Sun 4 OctRoodeschool 10:18No data—
Sun 27 SeptGroningen Europapark 09:23No data—
Sun 20 SeptRoodeschool 10:19No data—
Sun 13 SeptRoodeschool 10:18No data—
Sun 6 SeptRoodeschool 10:20No data—
Sun 30 AugRoodeschool 10:18No data—
Sun 23 AugRoodeschool 10:18No data—