Train Arriva 37619 Winschoten – Eemshaven

Winschoten 07:09 → Eemshaven 08: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 08:48 0 min

  1. Winschoten07:09
  2. Hoogezand-Sappemeer07:26
  3. Groningen Europapark07:40
  4. Sauwerd08:00
  5. Baflo08:09
  6. Roodeschool08:34
  7. Eemshaven08:42

Next service: tomorrow 07:09 from Winschoten · Tue 10 Nov

Next departure 07:09 tomorrow · Winschoten
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 1 full · 13 partial · 11 no data
On-time · 90 days
100%
19/19 runs under 3 min
RT coverage: 1 full · 18 partial · 57 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

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

Stops and timetable

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

Last 90 days, 19 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
07:09on time on time
07:13 / 07:15— —
07:21— —
07:26— —
07:29— —
07:31— —
07:40— —
07:43 / 07:47— —
07:51 / 07:54— —
08:00— —
08:05— —
08:09 / 08:10— —
08:15— —
08:19 / 08:20— —
08:25— —
08:29 / 08:30— —
08:34— —
08: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
Mon 9 NovRoodeschool 08:48Partial coverage0 min—
Sat 7 NovRoodeschool 08:49Partial coverage0 min—
Fri 6 NovRoodeschool 08:49No data—
Thu 5 NovRoodeschool 08:49No data—
Wed 4 NovRoodeschool 08:48Partial coverage0 min—
Tue 3 NovRoodeschool 08:48No data—
Mon 2 NovRoodeschool 08:49No data—
Sat 31 OctRoodeschool 08:48Partial coverage0 min—
Fri 30 OctRoodeschool 08:48Partial coverage0 min—
Thu 29 OctRoodeschool 08:48Partial coverage0 min—
Wed 28 OctRoodeschool 08:48Partial coverage0 min—
Tue 27 OctRoodeschool 08:48Partial coverage0 min—
Mon 26 OctRoodeschool 08:49Partial coverage0 min—
Sat 24 OctRoodeschool 08:48Partial coverage0 min—
Fri 23 OctRoodeschool 08:48Partial coverage0 min—
Thu 22 OctRoodeschool 08:48No data—
Wed 21 OctRoodeschool 08:48No data—
Tue 20 OctRoodeschool 08:48Partial coverage0 min—
Mon 19 OctRoodeschool 08:48Partial coverage0 min—
Sat 17 OctGroningen Europapark 07:55+1 min+2 min
Fri 16 OctGroningen Europapark 07:55No data—
Thu 15 OctRoodeschool 08:48No data—
Wed 14 OctRoodeschool 08:49No data—
Tue 13 OctRoodeschool 08:48No data—
Mon 12 OctRoodeschool 08:49No data—
Sat 10 OctRoodeschool 08:48Partial coverage0 min—
Fri 9 OctRoodeschool 08:50Partial coverage0 min+1 min
Thu 8 OctRoodeschool 08:49Partial coverage0 min—
Wed 7 OctRoodeschool 08:48Partial coverage0 min—
Tue 6 OctRoodeschool 08:50Partial coverage+2 min+2 min