Train Arriva 37647 Winschoten – Eemshaven

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

Running now · updated 14:35

Heading to Eemshaven 0 min

Estimated arrival at Eemshaven 15:42 · 71 km/h

  1. Winschoten14:09
  2. Hoogezand-Sappemeer14:26
  3. Groningen Europapark14:40
  4. Sauwerd15:00
  5. Baflo15:09
  6. Uithuizen15:25
  7. Eemshaven15:42

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 11 runs arrived on time.

On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 0 full · 11 partial · 15 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
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

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=3
  • 100% W n=3
  • — T n=0
  • 100% F n=1
  • 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 10Today
14:09on time on time
14:13 / 14:15— —
14:21— —
14:26— —
14:29— —
14:31— —
14:40— —
14:43 / 14:47— —
14:51 / 14:54— —
15:00— —
15:05— —
15:09 / 15:10— —
15:15— —
15:19 / 15:20— —
15:25— —
15:29 / 15:30— —
15:34— —
15: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 NovGroningen Europapark 14:34Partial coverage0 min—
Mon 9 NovRoodeschool 15:48Partial coverage0 min—
Sat 7 NovRoodeschool 15:49Partial coverage0 min—
Fri 6 NovRoodeschool 15:48No data—
Thu 5 NovUithuizermeeden 15:50No data—
Wed 4 NovRoodeschool 15:48Partial coverage0 min—
Tue 3 NovRoodeschool 15:48No data—
Mon 2 NovRoodeschool 15:49No data—
Sat 31 OctRoodeschool 15:48Partial coverage0 min—
Fri 30 OctRoodeschool 15:53No data—
Thu 29 OctRoodeschool 15:48No data—
Wed 28 OctRoodeschool 15:48Partial coverage0 min—
Tue 27 OctUithuizermeeden 15:52Partial coverage0 min—
Mon 26 OctRoodeschool 15:48No data—
Sat 24 OctRoodeschool 15:48Partial coverage0 min—
Fri 23 OctRoodeschool 15:49No data—
Thu 22 OctRoodeschool 15:50No data—
Wed 21 OctRoodeschool 15:48No data—
Tue 20 OctRoodeschool 15:49Partial coverage0 min—
Mon 19 OctRoodeschool 15:49Partial coverage0 min—
Sat 17 OctGroningen Europapark 14:54No data—
Fri 16 OctGroningen Europapark 14:54No data—
Thu 15 OctRoodeschool 15:49No data—
Wed 14 OctRoodeschool 15:48No data—
Tue 13 OctRoodeschool 15:48No data—
Mon 12 OctRoodeschool 15:48Partial coverage0 min—
Sat 10 OctRoodeschool 15:48Partial coverage0 min—
Fri 9 OctRoodeschool 15:49Partial coverage+1 min—
Thu 8 OctRoodeschool 15:48No data—
Wed 7 OctRoodeschool 15:48Partial coverage0 min—