Train Arriva 37960 Groningen – Winschoten

Groningen 17:08 → Winschoten 17:34 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 4 stops Arriva

Running now · updated 17:07

Heading to Winschoten No data

Estimated arrival at Winschoten 17:34

  1. Groningen17:08
  2. Groningen Europapark17:10
  3. Scheemda17:29
  4. Winschoten17:34
On-time · 30 days
82%
9/11 runs under 3 min
RT coverage: 1 full · 10 partial · 11 no data
On-time · 90 days
85%
11/13 runs under 3 min
RT coverage: 1 full · 12 partial · 50 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

Worst days

  • Wed 7 Oct Max en route +13 min · last fix heading to Scheemda +13 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Scheemda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 85% · 11
  • 3–10 min 8% · 1
  • 10–30 min 8% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 50% W n=2
  • 100% T n=2
  • 0% F n=1
  • — S n=0
  • — S n=0

Stops and timetable

Timetable of the latest run from the operator’s GTFS (4 stops).

Last 90 days, 13 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
17:08on time +2 min
17:10— —
17:29 / 17:30— —
17:34— —

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 NovGroningen 17:04No data—
Wed 4 NovScheemda 17:44No data—
Tue 3 NovScheemda 17:44Partial coverage0 min—
Mon 2 NovScheemda 17:39Partial coverage0 min—
Fri 30 OctScheemda 17:45No data—
Thu 29 OctScheemda 17:44Partial coverage0 min—
Wed 28 OctScheemda 17:44Partial coverage0 min—
Tue 27 OctScheemda 17:44Partial coverage0 min—
Mon 26 OctScheemda 17:44No data—
Fri 23 OctScheemda 17:44No data—
Thu 22 OctScheemda 17:44No data—
Wed 21 OctScheemda 17:44No data—
Tue 20 OctScheemda 17:44Partial coverage0 min—
Mon 19 OctScheemda 17:44Partial coverage0 min—
Fri 16 OctScheemda 17:45No data—
Thu 15 OctScheemda 17:44No data—
Wed 14 OctScheemda 17:44No data—
Tue 13 OctScheemda 17:44No data—
Mon 12 OctScheemda 17:44Partial coverage0 min—
Fri 9 OctScheemda 17:44+3 min+3 min
Thu 8 OctScheemda 17:45Partial coverage+2 min+2 min
Wed 7 OctScheemda 17:47Partial coverage+13 min+13 min
Tue 6 OctScheemda 17:44Partial coverage+3 min+3 min
Mon 5 OctScheemda 17:44Partial coverage0 min—
Fri 2 OctScheemda 17:44No data—
Thu 1 OctScheemda 17:44No data—
Wed 30 SeptScheemda 17:44No data—
Tue 29 SeptScheemda 17:44No data—
Mon 28 SeptScheemda 17:44No data—
Fri 25 SeptScheemda 17:44No data—