Train Arriva 20125 Bad Nieuweschans – Groningen

Bad Nieuweschans 18:46 → Groningen 19:27 Daily 0 h 41 min · 5 stops Arriva

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 18:46 from Bad Nieuweschans · Sun 8 Nov

Next departure 18:46 today · Bad Nieuweschans
On-time · 30 days
75%
3/4 runs under 3 min
RT coverage: 3 full · 1 partial · 4 no data
On-time · 90 days
71%
5/7 runs under 3 min
RT coverage: 6 full · 1 partial · 4 no data
Typical delay
0min
Median at arrival, 90 days
P90
+28min
9 in 10 runs arrive with less than this

Last 30 days

Arrival delay at Groningen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 2 Nov Max en route +59 min · last fix heading to — +59 min
  • Mon 5 Oct Max en route +8 min · last fix heading to — +7 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 71% · 5
  • 3–10 min 14% · 1
  • 10–30 min 0% · 0
  • 30+ min 14% · 1

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (5 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
18:46on time +29 min
18:55≈ on time ≈ +34 min
18:59 / 19:00≈ on time ≈ +34 min
19:22 / 19:24≈ +1 min ≈ +33 min
19:27+1 min +33 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
Sat 7 NovGroningen Europapark 19:38Partial coverage0 min—
Mon 2 Nov— 19:59+59 min+59 min
Sun 1 NovGroningen Europapark 19:39+2 min+6 min
Sat 31 OctGroningen Europapark 19:380 min—
Fri 30 OctBad Nieuweschans 19:03No data—
Mon 26 Oct— 19:08No data—
Sun 25 OctGroningen Europapark 19:38No data—
Sat 24 OctGroningen Europapark 19:38No data—
Wed 7 Oct— 19:000 min—
Tue 6 Oct— 19:000 min—
Mon 5 Oct— 19:08+7 min+8 min