Train Arriva 37646 Eemshaven – Winschoten

Eemshaven 12:48 → Winschoten 14: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 14:29 0 min

  1. Eemshaven12:48
  2. Uithuizen13:06
  3. Baflo13:20
  4. Groningen Noord13:35
  5. Groningen Europapark13:49
  6. Scheemda14:14
  7. Winschoten14:20

Next service: Monday 12:48 from Eemshaven · Mon 9 Nov

Next departure 12:48 Monday · Eemshaven
On-time · 30 days
100%
15/15 runs under 3 min
RT coverage: 11 full · 4 partial · 11 no data
On-time · 90 days
100%
18/18 runs under 3 min
RT coverage: 14 full · 4 partial · 59 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

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

  • Early 0% · 0
  • On time 100% · 18
  • 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=5
  • 100% W n=3
  • 100% T n=1
  • 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, 18 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
12:48on time on time
12:55≈ on time ≈ on time
12:59 / 13:02≈ on time ≈ on time
13:06≈ on time ≈ on time
13:11≈ on time ≈ on time
13:15≈ on time ≈ on time
13:20≈ on time ≈ on time
13:24 / 13:25≈ on time ≈ on time
13:30≈ on time ≈ on time
13:35 / 13:38≈ on time ≈ on time
13:43 / 13:47≈ on time ≈ on time
13:49≈ on time ≈ on time
13:58≈ on time ≈ on time
14:00≈ on time ≈ on time
14:03≈ on time ≈ on time
14:08≈ on time ≈ on time
14:14 / 14:15≈ on time ≈ on time
14: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
Sat 7 NovScheemda 14:29Partial coverage0 min—
Fri 6 NovScheemda 14:29No data—
Thu 5 NovScheemda 14:29No data—
Wed 4 NovScheemda 14:290 min+5 min
Tue 3 NovScheemda 14:290 min—
Mon 2 NovScheemda 14:290 min—
Sat 31 OctScheemda 14:30Partial coverage0 min+1 min
Fri 30 OctScheemda 14:29No data—
Thu 29 OctScheemda 14:290 min—
Wed 28 OctScheemda 14:290 min—
Tue 27 OctScheemda 14:290 min—
Mon 26 OctScheemda 14:290 min—
Sat 24 OctScheemda 14:29Partial coverage0 min—
Fri 23 OctScheemda 14:29No data—
Thu 22 OctScheemda 14:29No data—
Wed 21 OctScheemda 14:29No data—
Tue 20 OctScheemda 14:290 min—
Mon 19 OctScheemda 14:290 min—
Sat 17 OctScheemda 14:29No data—
Fri 16 OctScheemda 14:29No data—
Thu 15 OctScheemda 14:29No data—
Wed 14 OctScheemda 14:29No data—
Tue 13 OctScheemda 14:290 min—
Mon 12 OctScheemda 14:29No data—
Sat 10 OctScheemda 14:29Partial coverage0 min—
Fri 9 OctScheemda 14:290 min—
Thu 8 OctScheemda 14:29No data—
Wed 7 OctScheemda 14:290 min—
Tue 6 OctScheemda 14:290 min—
Mon 5 OctScheemda 14:290 min—