Train Arriva 37629 Bad Nieuweschans – Eemshaven
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 09:27 from Bad Nieuweschans · Thu 5 Nov
Last 30 days
Arrival delay at Eemshaven, 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
17 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 17
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=5
- 100% W n=4
- 100% T n=3
- 100% F n=1
- 100% S n=2
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (19 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 09:27 | on time | on time | |
| 09:36 / 09:39 | ≈ on time | ≈ on time | |
| 09:43 / 09:45 | ≈ on time | ≈ on time | |
| 09:51 | ≈ on time | ≈ on time | |
| 09:56 | ≈ on time | ≈ on time | |
| 09:59 | ≈ on time | ≈ on time | |
| 10:01 | ≈ on time | ≈ on time | |
| 10:10 | ≈ on time | ≈ on time | |
| 10:13 / 10:17 | ≈ on time | ≈ on time | |
| 10:21 / 10:24 | ≈ on time | ≈ on time | |
| 10:30 | ≈ on time | ≈ on time | |
| 10:35 | ≈ on time | ≈ on time | |
| 10:39 / 10:40 | ≈ on time | ≈ on time | |
| 10:45 | ≈ on time | ≈ on time | |
| 10:49 / 10:50 | ≈ on time | ≈ +1 min | |
| 10:55 | ≈ on time | ≈ +1 min | |
| 10:59 / 11:00 | ≈ on time | ≈ +1 min | |
| 11:04 | ≈ on time | ≈ +1 min | |
| 11:12 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Roodeschool 11:19Partial coverage | +1 min | +1 min |
| Tue 3 Nov | Roodeschool 11:18 | 0 min | — |
| Mon 2 Nov | Roodeschool 11:39Partial coverage | 0 min | — |
| Sat 31 Oct | Roodeschool 11:18 | No data | — |
| Fri 30 Oct | Roodeschool 11:19 | No data | — |
| Thu 29 Oct | Roodeschool 11:18Partial coverage | 0 min | — |
| Wed 28 Oct | Roodeschool 11:18Partial coverage | 0 min | — |
| Tue 27 Oct | Roodeschool 11:18 | 0 min | — |
| Mon 26 Oct | Roodeschool 11:18 | No data | — |
| Sat 24 Oct | Roodeschool 11:19 | +1 min | — |
| Fri 23 Oct | Roodeschool 11:19 | No data | — |
| Thu 22 Oct | Roodeschool 11:18Partial coverage | 0 min | — |
| Wed 21 Oct | Roodeschool 11:23Partial coverage | 0 min | — |
| Tue 20 Oct | Roodeschool 11:19 | 0 min | — |
| Mon 19 Oct | Roodeschool 11:18Partial coverage | 0 min | — |
| Sat 17 Oct | Groningen Europapark 10:24 | No data | — |
| Fri 16 Oct | Groningen Europapark 10:24 | No data | — |
| Thu 15 Oct | Roodeschool 11:18 | No data | — |
| Wed 14 Oct | Roodeschool 11:18 | No data | — |
| Tue 13 Oct | Roodeschool 11:19 | 0 min | — |
| Mon 12 Oct | Roodeschool 11:21 | No data | — |
| Sat 10 Oct | Roodeschool 11:19 | +1 min | — |
| Fri 9 Oct | Roodeschool 11:18 | 0 min | — |
| Thu 8 Oct | Roodeschool 11:18Partial coverage | 0 min | — |
| Wed 7 Oct | Groningen Noord 12:02Partial coverage | 0 min | — |
| Tue 6 Oct | Roodeschool 11:18 | 0 min | — |
| Mon 5 Oct | Roodeschool 11:19 | No data | — |
| Sat 3 Oct | Roodeschool 11:19 | No data | — |
| Fri 2 Oct | Roodeschool 11:18 | No data | — |
| Thu 1 Oct | Roodeschool 11:19 | No data | — |