Train Arriva 37658 Eemshaven – Winschoten

Eemshaven 15:48 → Winschoten 17:20 Mon, Tue, Wed, Thu, Fri, Sat 1 h 32 min · 18 stops Arriva

It does not run today

Last recorded run: Saturday 7 November +1 min

Next service: tomorrow 15:48 from Eemshaven · Mon 9 Nov

Next departure 15:48 tomorrow · Eemshaven
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%
15/15 runs under 3 min
RT coverage: 0 full · 15 partial · 61 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

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

  • Early 0% · 0
  • On time 100% · 15
  • 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=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, 15 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
15:48on time on time
15:55— —
15:59 / 16:02— —
16:06— —
16:11— —
16:15— —
16:20— —
16:24 / 16:25— —
16:30— —
16:35 / 16:38— —
16:43 / 16:47— —
16:49— —
16:58— —
17:00— —
17:03— —
17:08— —
17:14 / 17:15— —
17:20— —

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