Train Arriva 20116 Groningen – Bad Nieuweschans

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

✓ Today’s run finished

Today, last fix heading to Winschoten at 12:19 No data

  1. Groningen11:32
  2. Groningen Europapark11:34
  3. Scheemda11:59
  4. Winschoten12:04
  5. Bad Nieuweschans12:13

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

Next departure 11:32 tomorrow · Groningen
On-time · 30 days
92%
11/12 runs under 3 min
RT coverage: 10 full · 2 partial · 8 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 14 full · 2 partial · 9 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 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

  • Sun 1 Nov Max en route +4 min · last fix heading to Bad Nieuweschans +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=3
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • — F n=0
  • 100% S n=4
  • 67% S n=3

Stops and timetable

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

Last 90 days, 16 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
11:32on time on time
11:34 / 11:35≈ on time ≈ on time
11:59 / 12:00≈ on time ≈ +2 min
12:04 / 12:05≈ on time ≈ +2 min
12:13on time +3 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 12:19No data—
Sat 7 NovWinschoten 12:19Partial coverage+1 min+1 min
Sun 1 NovBad Nieuweschans 12:34+4 min+4 min
Sat 31 OctBad Nieuweschans 12:32+3 min+3 min
Fri 30 OctBad Nieuweschans 12:29No data—
Thu 29 OctBad Nieuweschans 12:300 min—
Wed 28 OctBad Nieuweschans 12:290 min—
Tue 27 OctBad Nieuweschans 12:280 min—
Mon 26 OctBad Nieuweschans 12:290 min—
Sun 25 OctWinschoten 12:20No data—
Sat 24 OctWinschoten 12:19Partial coverage+1 min+1 min
Sun 18 OctBad Nieuweschans 12:280 min—
Sat 17 OctBad Nieuweschans 12:32No data—
Fri 16 OctBad Nieuweschans 12:29No data—
Thu 15 OctBad Nieuweschans 12:28No data—
Wed 14 OctBad Nieuweschans 12:29No data—
Tue 13 OctBad Nieuweschans 12:30No data—
Mon 12 OctBad Nieuweschans 12:300 min—
Sun 11 OctBad Nieuweschans 12:32+3 min+3 min
Sat 10 OctBad Nieuweschans 12:360 min+6 min
Fri 9 OctBad Nieuweschans 12:28No data—
Thu 8 OctBad Nieuweschans 12:290 min—
Wed 7 OctBad Nieuweschans 12:280 min—
Tue 6 OctBad Nieuweschans 12:300 min—
Mon 5 OctBad Nieuweschans 12:280 min—