Train Arriva 20121 Bad Nieuweschans – Groningen

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

It has not run yet today

Last recorded run: Sunday 8 November 0 min

Next service: today 16:46 from Bad Nieuweschans · Mon 9 Nov

Next departure 16:46 today · Bad Nieuweschans
On-time · 30 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 5 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 13 full · 1 partial · 5 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: +1 min

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

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 100% · 14
  • 3–10 min 0% · 0
  • 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=3
  • 100% S n=2

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
16:46on time on time
16:55≈ on time ≈ on time
16:59 / 17:00≈ on time ≈ +1 min
17:22 / 17:24≈ on time ≈ +2 min
17:27on time +2 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 NovGroningen Europapark 17:38Partial coverage0 min—
Sat 7 NovGroningen Europapark 17:38+2 min+2 min
Fri 6 NovBad Nieuweschans 17:03No data—
Thu 5 NovBad Nieuweschans 17:030 min—
Wed 4 NovBad Nieuweschans 17:040 min—
Tue 3 NovBad Nieuweschans 17:030 min—
Mon 2 NovBad Nieuweschans 17:030 min—
Sun 1 NovGroningen Europapark 17:380 min—
Sat 31 OctGroningen Europapark 17:380 min—
Fri 30 OctBad Nieuweschans 17:03No data—
Thu 29 OctBad Nieuweschans 17:030 min—
Mon 26 Oct— 17:020 min—
Sun 25 OctGroningen Europapark 17:38No data—
Sat 24 OctGroningen Europapark 17:38No data—
Sat 17 Oct— 17:28No data—
Sat 10 Oct— 17:280 min—
Wed 7 Oct— 17:020 min—
Tue 6 Oct— 17:010 min—
Mon 5 Oct— 17:03+3 min+4 min