Train Arriva 20128 Groningen – Bad Nieuweschans

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

It has not run yet today

Last recorded run: Sunday 8 November +1 min

Next service: today 17:32 from Groningen · Mon 9 Nov

Next departure 17:32 today · Groningen
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 8 no data
On-time · 90 days
93%
13/14 runs under 3 min
RT coverage: 13 full · 1 partial · 8 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: +2 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 +6 min · last fix heading to Bad Nieuweschans +6 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 93% · 13
  • 3–10 min 7% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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