Train Arriva 37618 Roodeschool – Winschoten

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

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 05:57 from Roodeschool · Mon 9 Nov

Next departure 05:57 today · Roodeschool
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 18 full · 3 partial · 3 no data
On-time · 90 days
100%
26/26 runs under 3 min
RT coverage: 22 full · 4 partial · 49 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 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

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

  • Early 0% · 0
  • On time 100% · 26
  • 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=5
  • — S n=0

Stops and timetable

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

Last 90 days, 26 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:57on time on time
06:01 / 06:02≈ on time ≈ on time
06:06≈ on time ≈ on time
06:11≈ on time ≈ on time
06:15≈ on time ≈ on time
06:20≈ on time ≈ +1 min
06:24 / 06:25≈ on time ≈ +1 min
06:30≈ on time ≈ +1 min
06:35 / 06:38≈ on time ≈ +1 min
06:43 / 06:47≈ on time ≈ +1 min
06:49≈ on time ≈ +1 min
06:58≈ on time ≈ +1 min
07:00≈ on time ≈ +1 min
07:03≈ on time ≈ +2 min
07:08≈ on time ≈ +2 min
07:14 / 07:15≈ on time ≈ +2 min
07:20on time +2 min

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