Train Arriva 37615 Winschoten – Eemshaven

Winschoten 06:09 → Eemshaven 07:42 Mon, Tue, Wed, Thu, Fri, Sat 1 h 33 min · 18 stops Arriva

✓ Today’s run finished

Today, last fix heading to Roodeschool at 07:49 +1 min

  1. Winschoten06:09
  2. Hoogezand-Sappemeer06:26
  3. Groningen Europapark06:40
  4. Sauwerd07:00
  5. Baflo07:09
  6. Roodeschool07:34
  7. Eemshaven07:42

Next service: tomorrow 06:09 from Winschoten · Thu 12 Nov

Next departure 06:09 tomorrow · Winschoten
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 3 full · 18 partial · 4 no data
On-time · 90 days
96%
26/27 runs under 3 min
RT coverage: 4 full · 23 partial · 47 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: +1 min

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

Worst days

  • Tue 6 Oct Max en route +7 min · last fix heading to Roodeschool +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 26
  • 3–10 min 4% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 83% T n=6
  • 100% W n=6
  • 100% T n=4
  • 100% F n=4
  • 100% S n=3
  • — S n=0

Stops and timetable

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

Last 90 days, 27 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
06:09on time on time
06:13 / 06:15— —
06:21— —
06:26— —
06:29— —
06:31— —
06:40— —
06:43 / 06:47— —
06:51 / 06:54— —
07:00— —
07:05— —
07:09 / 07:10— —
07:14 / 07:15— —
07:19 / 07:20— —
07:25— —
07:29 / 07:30— —
07:34— —
07:42— —

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
Wed 11 NovRoodeschool 07:49Partial coverage+1 min+1 min
Tue 10 NovRoodeschool 07:49Partial coverage+2 min+2 min
Mon 9 NovRoodeschool 07:49Partial coverage+1 min+2 min
Sat 7 NovRoodeschool 07:480 min—
Fri 6 NovRoodeschool 07:49No data—
Thu 5 NovRoodeschool 07:49No data—
Wed 4 NovRoodeschool 07:48Partial coverage0 min—
Tue 3 NovRoodeschool 07:49Partial coverage0 min—
Mon 2 NovRoodeschool 07:49No data—
Sat 31 OctRoodeschool 07:48No data—
Fri 30 OctRoodeschool 07:50Partial coverage+2 min+2 min
Thu 29 OctRoodeschool 07:50Partial coverage+1 min+2 min
Wed 28 OctRoodeschool 07:51Partial coverage0 min—
Tue 27 OctRoodeschool 07:51Partial coverage0 min—
Mon 26 OctUithuizermeeden 08:04Partial coverage0 min+5 min
Sat 24 OctRoodeschool 07:480 min—
Fri 23 OctRoodeschool 07:49Partial coverage+1 min—
Thu 22 OctRoodeschool 07:50Partial coverage+1 min—
Wed 21 OctRoodeschool 07:59Partial coverage0 min—
Tue 20 OctRoodeschool 07:50Partial coverage0 min—
Mon 19 OctRoodeschool 07:51Partial coverage0 min—
Fri 16 OctGroningen Europapark 06:540 min—
Thu 15 OctRoodeschool 07:52Partial coverage0 min—
Wed 14 OctRoodeschool 07:49Partial coverage0 min—
Tue 13 OctRoodeschool 07:48Partial coverage0 min—
Mon 12 OctRoodeschool 07:50Partial coverage0 min—
Sat 10 OctRoodeschool 07:49+1 min—
Fri 9 OctRoodeschool 07:49Partial coverage+1 min—
Thu 8 OctRoodeschool 07:49Partial coverage0 min—
Wed 7 OctRoodeschool 07:50Partial coverage+2 min+2 min