Train Arriva 37659 Winschoten – Eemshaven

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 17:09 from Winschoten · Wed 11 Nov

Next departure 17:09 today · Winschoten
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 14 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 1 full · 17 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=3
  • 100% W n=3
  • 100% T n=1
  • 100% F n=2
  • 100% S n=4
  • — S n=0

Stops and timetable

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

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