Train Arriva 37649 Winschoten – Eemshaven

Winschoten 14:39 → Eemshaven 16:12 Mon, Tue, Wed, Thu, Fri, Sat 1 h 33 min · 18 stops Arriva

It has not run yet today

Last recorded run: Saturday 14 November 0 min

Next service: today 14:39 from Winschoten · Mon 16 Nov

Next departure 14:39 today · Winschoten
On-time · 30 days
100%
14/14 runs under 3 min
RT coverage: 11 full · 3 partial · 10 no data
On-time · 90 days
100%
21/21 runs under 3 min
RT coverage: 17 full · 4 partial · 54 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

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

  • Early 0% · 0
  • On time 100% · 21
  • 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=4
  • 100% W n=4
  • 100% T n=3
  • 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, 21 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
14:39on time on time
14:43 / 14:45≈ on time ≈ on time
14:51≈ on time ≈ on time
14:56≈ on time ≈ on time
14:59≈ on time ≈ on time
15:01≈ on time ≈ on time
15:10≈ on time ≈ on time
15:13 / 15:17≈ on time ≈ on time
15:21 / 15:24≈ on time ≈ on time
15:30≈ on time ≈ on time
15:35≈ on time ≈ on time
15:39 / 15:40≈ on time ≈ on time
15:45≈ on time ≈ on time
15:49 / 15:50≈ on time ≈ on time
15:55≈ on time ≈ on time
15:59 / 16:00≈ on time ≈ on time
16:04≈ on time ≈ on time
16:12on 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 14 NovRoodeschool 16:18Partial coverage0 min—
Fri 13 NovRoodeschool 16:180 min—
Thu 12 NovRoodeschool 16:190 min—
Wed 11 NovRoodeschool 16:180 min—
Tue 10 NovUithuizermeeden 16:340 min+12 min
Mon 9 NovRoodeschool 16:180 min—
Sat 7 NovRoodeschool 16:18Partial coverage0 min—
Fri 6 NovRoodeschool 16:19No data—
Thu 5 NovRoodeschool 16:20No data—
Wed 4 NovRoodeschool 16:190 min—
Tue 3 NovRoodeschool 16:19No data—
Mon 2 NovRoodeschool 16:19No data—
Sat 31 OctRoodeschool 16:18No data—
Fri 30 OctRoodeschool 16:19No data—
Thu 29 OctRoodeschool 16:18No data—
Wed 28 OctRoodeschool 16:280 min—
Tue 27 OctRoodeschool 16:180 min—
Mon 26 OctRoodeschool 16:18No data—
Sat 24 OctRoodeschool 16:34Partial coverage0 min+15 min
Fri 23 OctRoodeschool 16:19No data—
Thu 22 OctRoodeschool 16:200 min—
Wed 21 OctRoodeschool 16:18No data—
Tue 20 OctRoodeschool 16:210 min—
Mon 19 OctRoodeschool 16:190 min—
Sat 17 OctGroningen Europapark 15:24No data—
Fri 16 OctGroningen Europapark 15:24No data—
Thu 15 OctRoodeschool 16:18No data—
Wed 14 OctRoodeschool 16:18No data—
Tue 13 OctRoodeschool 16:18No data—
Mon 12 OctRoodeschool 16:180 min—