Train Arriva 37946 Groningen – Winschoten

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

It does not run today

Last recorded run: Friday 6 November No data

Next service: Monday 13:38 from Groningen · Mon 9 Nov

Next departure 13:38 Monday · Groningen
On-time · 30 days
80%
4/5 runs under 3 min
RT coverage: 0 full · 5 partial · 16 no data
On-time · 90 days
86%
6/7 runs under 3 min
RT coverage: 0 full · 7 partial · 73 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 86% · 6
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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