Train Arriva 37569 Veendam – Roodeschool

Veendam 19:44 → Roodeschool 21:04 Sun 1 h 20 min · 16 stops Arriva

It does not run today

Last recorded run: Sunday 15 November 0 min

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

Next departure 19:44 Sunday · Veendam
On-time · 30 days
100%
3/3 runs under 3 min
RT coverage: 0 full · 3 partial · 1 no data
On-time · 90 days
100%
5/5 runs under 3 min
RT coverage: 1 full · 4 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 Roodeschool, 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 (16 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
19:44on time on time
19:50— —
19:56— —
19:59— —
20:01— —
20:09— —
20:13 / 20:20— —
20:24— —
20:30— —
20:35— —
20:39 / 20:40— —
20:45— —
20:49 / 20:50— —
20:55— —
20:59 / 21:00— —
21:04— —

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 NovUithuizermeeden 21:14Partial coverage0 min—
Sun 8 NovUithuizermeeden 21:14Partial coverage0 min—
Sun 1 NovUithuizermeeden 21:14Partial coverage+1 min+1 min
Sun 25 OctUithuizermeeden 21:14No data—
Sun 18 OctGroningen Europapark 20:250 min—
Sun 11 OctUithuizermeeden 21:14Partial coverage0 min—
Sun 4 OctUithuizermeeden 21:14No data—
Sun 27 SeptGroningen Europapark 20:23No data—
Sun 20 SeptUithuizermeeden 21:17No data—
Sun 13 SeptUithuizermeeden 21:16No data—
Sun 6 SeptUithuizermeeden 21:14No data—
Sun 30 AugUithuizermeeden 21:14No data—
Sun 23 AugUithuizermeeden 21:14No data—