Train Arriva 37618 Roodeschool – Winschoten

Roodeschool 05:55 → Winschoten 07:20 Mon, Tue, Wed, Thu, Fri, Sat 1 h 25 min · 17 stops Arriva

✓ Today’s run finished

Today, last fix heading to Scheemda at 07:29 0 min

  1. Roodeschool05:55
  2. Usquert06:11
  3. Baflo06:20
  4. Groningen Noord06:35
  5. Kropswolde06:58
  6. Scheemda07:14
  7. Winschoten07:20

Next service: tomorrow 05:55 from Roodeschool · Fri 6 Nov

Next departure 05:55 tomorrow · Roodeschool
On-time · 30 days
100%
24/24 runs under 3 min
RT coverage: 4 full · 20 partial · 2 no data
On-time · 90 days
100%
25/25 runs under 3 min
RT coverage: 4 full · 21 partial · 51 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

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

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

  • Early 0% · 0
  • On time 100% · 25
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=3
  • 100% S n=4
  • — S n=0

Stops and timetable

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

Last 90 days, 25 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
05:55on time on time
05:59 / 06:02— —
06:06— —
06:11— —
06:15— —
06:20— —
06:24 / 06:25— —
06:30— —
06:35 / 06:38— —
06:43 / 06:47— —
06:49— —
06:58— —
07:00— —
07:03— —
07:08— —
07:14 / 07:15— —
07:20— —

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
Thu 5 NovScheemda 07:29Partial coverage0 min—
Wed 4 NovScheemda 07:29Partial coverage0 min—
Tue 3 NovScheemda 07:29Partial coverage+2 min+2 min
Mon 2 NovScheemda 07:29No data—
Sat 31 OctScheemda 07:290 min—
Fri 30 OctScheemda 07:30Partial coverage+1 min—
Thu 29 OctScheemda 07:29Partial coverage+1 min—
Wed 28 OctScheemda 07:29Partial coverage0 min—
Tue 27 OctScheemda 07:29Partial coverage0 min—
Mon 26 OctScheemda 07:29Partial coverage0 min—
Sat 24 OctScheemda 07:29+1 min—
Fri 23 OctScheemda 07:29Partial coverage0 min—
Thu 22 OctScheemda 07:32Partial coverage+2 min+3 min
Wed 21 OctScheemda 07:30Partial coverage0 min—
Tue 20 OctScheemda 07:29Partial coverage0 min—
Mon 19 OctScheemda 07:29Partial coverage0 min—
Sat 17 OctScheemda 07:31+1 min+2 min
Fri 16 OctScheemda 07:29No data—
Thu 15 OctScheemda 07:29Partial coverage+1 min—
Wed 14 OctScheemda 07:29Partial coverage0 min—
Tue 13 OctScheemda 07:29Partial coverage0 min—
Mon 12 OctScheemda 07:29Partial coverage0 min—
Sat 10 OctScheemda 07:290 min—
Fri 9 OctScheemda 07:29Partial coverage0 min—
Thu 8 OctScheemda 07:32Partial coverage+2 min+3 min
Wed 7 OctScheemda 07:29Partial coverage0 min—
Tue 6 OctScheemda 07:30Partial coverage+1 min—
Mon 5 OctScheemda 07:30No data—
Sat 3 OctScheemda 07:40No data—
Fri 2 OctWinschoten 07:37No data—