Train Arriva 37942 Groningen – Winschoten

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

It has not run yet today

Last recorded run: Wednesday 4 November +5 min

Next service: today 12:38 from Groningen · Thu 5 Nov

Next departure 12:38 today · Groningen
On-time · 30 days
75%
6/8 runs under 3 min
RT coverage: 0 full · 8 partial · 13 no data
On-time · 90 days
80%
8/10 runs under 3 min
RT coverage: 0 full · 10 partial · 70 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: +4 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 4 Nov Max en route +5 min · last fix heading to Scheemda +5 min
  • Fri 9 Oct Max en route +3 min · last fix heading to Scheemda +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 80% · 8
  • 3–10 min 20% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 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, 10 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:38on time on time
12:40— —
12:59 / 13:00— —
13: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
Wed 4 NovScheemda 13:19Partial coverage+5 min+5 min
Tue 3 NovScheemda 13:14No data—
Mon 2 NovScheemda 13:14No data—
Fri 30 OctScheemda 13:14No data—
Thu 29 OctScheemda 13:14Partial coverage0 min—
Wed 28 OctScheemda 13:14Partial coverage0 min—
Tue 27 OctScheemda 13:18No data—
Mon 26 OctScheemda 13:14No data—
Fri 23 OctScheemda 13:15No data—
Thu 22 OctScheemda 13:17No data—
Wed 21 OctScheemda 13:14No data—
Tue 20 OctScheemda 13:14Partial coverage0 min—
Mon 19 OctScheemda 13:14Partial coverage0 min—
Fri 16 OctScheemda 13:14No data—
Thu 15 OctScheemda 13:16No data—
Wed 14 OctScheemda 13:14No data—
Tue 13 OctScheemda 13:15No data—
Mon 12 OctScheemda 13:14No data—
Fri 9 OctScheemda 13:15Partial coverage+3 min+3 min
Thu 8 OctScheemda 13:14Partial coverage0 min—
Wed 7 OctScheemda 13:15Partial coverage+1 min+1 min
Tue 6 OctScheemda 13:14Partial coverage0 min—
Mon 5 OctScheemda 13:14Partial coverage0 min—
Sun 4 OctWinschoten 13:19No data—
Sat 3 OctWinschoten 13:20No data—
Fri 2 OctWinschoten 13:19No data—
Thu 1 OctWinschoten 13:19No data—
Wed 30 SeptWinschoten 13:19No data—
Tue 29 SeptWinschoten 13:21No data—
Mon 28 SeptWinschoten 13:19No data—