Train Arriva 20120 Groningen – Bad Nieuweschans

Groningen 13:32 → Bad Nieuweschans 14: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: tomorrow 13:32 from Groningen · Sat 21 Nov

Next departure 13:32 tomorrow · Groningen
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 7 full · 1 partial · 3 no data
On-time · 90 days
94%
16/17 runs under 3 min
RT coverage: 16 full · 1 partial · 8 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

  • Sat 31 Oct Max en route +3 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 94% · 16
  • 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
  • 100% F n=1
  • 67% S n=3
  • 100% 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
13:32on time on time
13:34 / 13:35≈ on time ≈ on time
13:59 / 14:00≈ on time ≈ +1 min
14:04 / 14:05≈ on time ≈ +1 min
14:13on time +1 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 14:19Partial coverage+1 min+1 min
Sat 7 NovWinschoten 14:19+2 min+2 min
Sun 1 NovBad Nieuweschans 14:310 min—
Sat 31 OctBad Nieuweschans 14:32+3 min+3 min
Fri 30 OctBad Nieuweschans 14:34No data—
Thu 29 OctBad Nieuweschans 14:300 min—
Wed 28 OctBad Nieuweschans 14:290 min—
Tue 27 OctBad Nieuweschans 14:290 min—
Mon 26 OctBad Nieuweschans 14:290 min—
Sun 25 OctWinschoten 14:19No data—
Sat 24 OctWinschoten 14:19No data—
Sun 18 OctBad Nieuweschans 14:290 min—
Sat 17 OctBad Nieuweschans 14:30No data—
Fri 16 OctBad Nieuweschans 14:29No data—
Thu 15 OctBad Nieuweschans 14:32No data—
Wed 14 OctBad Nieuweschans 14:29No data—
Tue 13 OctBad Nieuweschans 14:28No data—
Mon 12 OctBad Nieuweschans 14:280 min—
Sun 11 OctBad Nieuweschans 14:280 min—
Sat 10 OctBad Nieuweschans 14:290 min—
Fri 9 OctBad Nieuweschans 14:290 min—
Thu 8 OctBad Nieuweschans 14:290 min—
Wed 7 OctBad Nieuweschans 14:280 min—
Tue 6 OctBad Nieuweschans 14:30+1 min—
Mon 5 OctBad Nieuweschans 14:290 min—