Train Arriva 37630 Eemshaven – Winschoten

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

✓ Today’s run finished

Today, last fix heading to Scheemda at 10:29 No data

  1. Eemshaven08:48
  2. Uithuizen09:06
  3. Baflo09:20
  4. Groningen Noord09:35
  5. Groningen Europapark09:49
  6. Scheemda10:14
  7. Winschoten10:20

Next service: tomorrow 08:48 from Eemshaven · Fri 6 Nov

Full trip card
Next departure 08:48 tomorrow · Eemshaven
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 5 full · 9 partial · 12 no data
On-time · 90 days
100%
15/15 runs under 3 min
RT coverage: 5 full · 10 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 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=2
  • 100% T n=3
  • 100% W n=3
  • 100% T n=2
  • 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 10
Eemshaven
08:48on time on time
Roodeschool
08:55≈ on time ≈ on time
Uithuizermeeden
08:59 / 09:02≈ on time ≈ on time
Uithuizen
09:06≈ on time ≈ on time
Usquert
09:11≈ on time ≈ on time
Warffum
09:15≈ on time ≈ on time
Baflo
09:20≈ on time ≈ on time
Winsum
09:24 / 09:25≈ on time ≈ on time
Sauwerd
09:30≈ on time ≈ on time
Groningen Noord
09:35 / 09:38≈ on time ≈ on time
Groningen
09:43 / 09:47≈ on time ≈ on time
Groningen Europapark
09:49≈ on time ≈ on time
Kropswolde
09:58≈ on time ≈ on time
Martenshoek
10:00≈ on time ≈ on time
Hoogezand-Sappemeer
10:03≈ on time ≈ on time
Zuidbroek
10:08≈ on time ≈ on time
Scheemda
10:14 / 10:15≈ on time ≈ on time
Winschoten
10:20on time on time

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