Train Arriva 37950 Groningen – Winschoten

Groningen 14:38 → Winschoten 15:04 Mon, Tue, Wed, Thu, Fri 0 h 26 min · 4 stops Arriva

It does not run today

Last recorded run: Friday 13 November +16 min

Next service: Monday 14:38 from Groningen · Mon 16 Nov

Next departure 14:38 Monday · Groningen
On-time · 30 days
89%
8/9 runs under 3 min
RT coverage: 0 full · 9 partial · 12 no data
On-time · 90 days
75%
9/12 runs under 3 min
RT coverage: 0 full · 12 partial · 66 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+16min
9 in 10 runs arrive with less than this
30 days: +5 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

  • Mon 5 Oct Max en route +20 min · last fix heading to Scheemda +20 min
  • Fri 13 Nov Max en route +16 min · last fix heading to Scheemda +16 min
  • Wed 7 Oct Max en route +9 min · last fix heading to Scheemda +9 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 75% · 9
  • 3–10 min 8% · 1
  • 10–30 min 17% · 2
  • 30+ min 0% · 0

On-time by weekday

  • 67% M n=3
  • 100% T n=3
  • 67% W n=3
  • 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, 12 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:38on time +1 min
14:40— —
14:59 / 15:00— —
15:04— —

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