Train Arriva 37636 Eemshaven – Winschoten

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

✓ Today’s run finished

Today, last fix heading to Scheemda at 11:59 0 min

  1. Eemshaven10:18
  2. Uithuizen10:36
  3. Baflo10:50
  4. Groningen Noord11:05
  5. Groningen Europapark11:19
  6. Scheemda11:44
  7. Winschoten11:50

Next service: Monday 10:18 from Eemshaven · Mon 9 Nov

Next departure 10:18 Monday · Eemshaven
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 9 full · 4 partial · 13 no data
On-time · 90 days
100%
16/16 runs under 3 min
RT coverage: 12 full · 4 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

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

  • Early 0% · 0
  • On time 100% · 16
  • 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=4
  • 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, 16 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
10:18on time on time
10:25≈ on time ≈ on time
10:29 / 10:32≈ on time ≈ on time
10:36≈ on time ≈ on time
10:41≈ on time ≈ on time
10:45≈ on time ≈ on time
10:50≈ on time ≈ on time
10:54 / 10:55≈ on time ≈ on time
11:00≈ on time ≈ on time
11:05 / 11:08≈ on time ≈ on time
11:13 / 11:17≈ on time ≈ on time
11:19≈ on time ≈ on time
11:28≈ on time ≈ on time
11:30≈ on time ≈ on time
11:33≈ on time ≈ on time
11:38≈ on time ≈ on time
11:44 / 11:45≈ on time ≈ on time
11:50on 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
Sat 7 NovScheemda 11:59Partial coverage0 min—
Fri 6 NovWinschoten 12:13No data—
Thu 5 NovWinschoten 12:12No data—
Wed 4 NovWinschoten 12:120 min—
Tue 3 NovWinschoten 12:14No data—
Mon 2 NovWinschoten 12:13No data—
Sat 31 OctScheemda 11:59Partial coverage0 min—
Fri 30 OctWinschoten 12:12No data—
Thu 29 OctWinschoten 12:12No data—
Wed 28 OctWinschoten 12:130 min—
Tue 27 OctWinschoten 12:120 min—
Mon 26 OctWinschoten 12:130 min—
Sat 24 OctScheemda 11:59Partial coverage0 min—
Fri 23 OctWinschoten 12:12No data—
Thu 22 OctWinschoten 12:120 min—
Wed 21 OctWinschoten 12:120 min—
Tue 20 OctWinschoten 12:120 min—
Mon 19 OctWinschoten 12:120 min—
Sat 17 OctScheemda 11:59No data—
Fri 16 OctWinschoten 12:12No data—
Thu 15 OctWinschoten 12:12No data—
Wed 14 OctWinschoten 12:12No data—
Tue 13 OctWinschoten 12:14No data—
Mon 12 OctWinschoten 12:13No data—
Sat 10 OctScheemda 11:59Partial coverage0 min—
Fri 9 OctWinschoten 12:120 min—
Thu 8 OctWinschoten 12:120 min—
Wed 7 OctWinschoten 12:120 min—
Tue 6 OctWinschoten 12:120 min—
Mon 5 OctWinschoten 12:12No data—