Train Arriva 37685 Bad Nieuweschans – Groningen
It has not run yet today
Last recorded run: Saturday 17 October No data
Next service: today 23:10 from Bad Nieuweschans · Sat 24 Oct
Next departure 23:10 today · Bad Nieuweschans
On-time · 30 days
—
Too little data (0/3 runs with data)
RT coverage: 0 full · 0 partial · 3 no data
On-time · 90 days
—
Too little data (0/7 runs with data)
RT coverage: 0 full · 0 partial · 7 no data
Typical delay
—
Needs at least 5 runs with data (0 so far)
P90
—
Needs at least 5 runs with data (0 so far)
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
No runs with a known final delay yet.
On-time by weekday
- — M n=0
- — T n=0
- — W n=0
- — T n=0
- — F n=0
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
| Stop | Sched. |
|---|---|
| 23:10 | |
| 23:18 / 23:19 | |
| 23:23 | |
| 23:30 | |
| 23:35 | |
| 23:38 | |
| 23:40 | |
| 23:48 | |
| 23:52 |
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.
Recent runs
| Date | Last stop | Final | Max |
|---|---|---|---|
| Sat 17 Oct | Groningen Europapark 00:03 | No data | — |
| Sat 3 Oct | Groningen Europapark 23:54 | No data | — |
| Sat 26 Sept | Kropswolde 23:54 | No data | — |
| Sat 12 Sept | Kropswolde 23:54 | No data | — |
| Sat 22 Aug | Groningen Europapark 00:02 | No data | — |
| Sat 15 Aug | Scheemda 23:37 | No data | — |
| Sat 8 Aug | Scheemda 23:37 | No data | — |