Train Arriva 37663 Winschoten – Eemshaven

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

It does not run today

Last recorded run: Saturday 7 November +1 min

Next service: tomorrow 18:09 from Winschoten · Mon 9 Nov

Next departure 18:09 tomorrow · Winschoten
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 1 full · 10 partial · 12 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 1 full · 12 partial · 48 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

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=1
  • 100% W n=2
  • — T n=0
  • 100% F n=3
  • 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, 13 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
18:09on time on time
18:13 / 18:15— —
18:21— —
18:26— —
18:29— —
18:31— —
18:40— —
18:43 / 18:47— —
18:51 / 18:54— —
19:00— —
19:05— —
19:09 / 19:10— —
19:15— —
19:19 / 19:20— —
19:25— —
19:29 / 19:30— —
19:34— —
19: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
Sat 7 NovRoodeschool 19:49Partial coverage+1 min—
Fri 6 NovGroningen 18:59Partial coverage0 min—
Thu 5 NovWinschoten 18:23No data—
Wed 4 NovScheemda 18:29Partial coverage0 min—
Tue 3 NovWinschoten 18:23No data—
Mon 2 NovWinschoten 18:23No data—
Sat 31 OctRoodeschool 19:48Partial coverage0 min—
Fri 30 OctGroningen Noord 19:08No data—
Wed 28 OctWinschoten 18:23Partial coverage0 min—
Mon 26 OctWinschoten 18:23Partial coverage0 min—
Sat 24 OctRoodeschool 19:49No data—
Fri 23 OctUithuizen 19:39Partial coverage0 min—
Thu 22 OctGroningen Europapark 18:54No data—
Wed 21 OctGroningen Europapark 18:57No data—
Tue 20 OctGroningen Europapark 18:50Partial coverage0 min—
Mon 19 OctGroningen Europapark 18:54Partial coverage0 min—
Sat 17 OctGroningen Europapark 18:54No data—
Fri 16 OctGroningen Europapark 18:54No data—
Thu 15 OctMartenshoek 18:43No data—
Wed 14 OctRoodeschool 19:48No data—
Tue 13 OctGroningen Europapark 18:50No data—
Mon 12 OctGroningen Europapark 18:54Partial coverage0 min—
Sat 10 OctRoodeschool 19:480 min—
Fri 9 OctKropswolde 18:45Partial coverage0 min—
Wed 7 OctWinschoten 18:23No data—
Mon 5 OctWinschoten 18:23Partial coverage0 min—
Sat 3 OctRoodeschool 19:49No data—
Fri 2 OctGroningen 19:01No data—
Sat 26 SeptGroningen Europapark 18:54No data—
Fri 25 SeptKropswolde 18:45No data—