Train Arriva 20118 Groningen – Bad Nieuweschans

Groningen 12:32 → Bad Nieuweschans 13:13 Daily 0 h 41 min · 5 stops Arriva

✓ Today’s run finished

Today, last fix heading to Winschoten at 13:19 +1 min

  1. Groningen12:32
  2. Groningen Europapark12:34
  3. Scheemda12:59
  4. Winschoten13:04
  5. Bad Nieuweschans13:13

Next service: tomorrow 12:32 from Groningen · Mon 9 Nov

Next departure 12:32 tomorrow · Groningen
On-time · 30 days
85%
11/13 runs under 3 min
RT coverage: 12 full · 1 partial · 9 no data
On-time · 90 days
82%
14/17 runs under 3 min
RT coverage: 16 full · 1 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+4min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

Arrival delay at Bad Nieuweschans, 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 +17 min · last fix heading to Bad Nieuweschans +17 min
  • Sat 10 Oct Max en route +6 min · last fix heading to Bad Nieuweschans +5 min
  • Sun 1 Nov Max en route +4 min · last fix heading to Bad Nieuweschans +3 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=2
  • 100% T n=2
  • 0% F n=1
  • 75% S n=4
  • 75% S n=4

Stops and timetable

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

Last 90 days, 17 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:32on time on time
12:34 / 12:35≈ on time ≈ +1 min
12:59 / 13:00≈ on time ≈ +3 min
13:04 / 13:05≈ on time ≈ +3 min
13:13on time +4 min

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
Sun 8 NovWinschoten 13:19Partial coverage+1 min+1 min
Sat 7 NovWinschoten 13:19+1 min+1 min
Thu 5 Nov— 13:23No data—
Mon 2 Nov— 13:19No data—
Sun 1 NovBad Nieuweschans 13:33+3 min+4 min
Sat 31 OctBad Nieuweschans 13:280 min—
Fri 30 OctBad Nieuweschans 13:28No data—
Thu 29 OctBad Nieuweschans 13:290 min—
Wed 28 OctBad Nieuweschans 13:290 min—
Tue 27 OctBad Nieuweschans 13:280 min—
Mon 26 OctBad Nieuweschans 13:290 min—
Sun 25 OctWinschoten 13:19No data—
Sat 24 OctWinschoten 13:20+3 min+3 min
Sun 18 OctBad Nieuweschans 13:280 min—
Sat 17 OctBad Nieuweschans 13:32No data—
Fri 16 OctBad Nieuweschans 13:28No data—
Thu 15 OctBad Nieuweschans 13:33No data—
Wed 14 OctBad Nieuweschans 13:28No data—
Tue 13 OctBad Nieuweschans 13:29No data—
Mon 12 OctBad Nieuweschans 13:290 min—
Sun 11 OctBad Nieuweschans 13:280 min—
Sat 10 OctBad Nieuweschans 13:33+5 min+6 min
Fri 9 OctBad Nieuweschans 13:46+17 min+17 min
Thu 8 OctBad Nieuweschans 13:290 min—
Wed 7 OctBad Nieuweschans 13:31+2 min+2 min
Tue 6 OctBad Nieuweschans 13:28No data—
Mon 5 OctBad Nieuweschans 13:290 min—