Train Arriva 37587 Groningen – Roodeschool
On-time · 30 days
—
Too little data (1/4 runs with data)
RT coverage: 0 full · 1 partial · 3 no data
On-time · 90 days
—
Too little data (1/11 runs with data)
RT coverage: 0 full · 1 partial · 10 no data
Typical delay
—
Needs at least 5 runs with data (1 so far)
P90
—
Needs at least 5 runs with data (1 so far)
Last 30 days
Arrival delay at Roodeschool, 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
1 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 100% · 1
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=1
- — 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 (10 stops).
| Stop | Sched. |
|---|---|
| 00:22 | |
| 00:26 | |
| 00:32 | |
| 00:37 | |
| 00:41 / 00:42 | |
| 00:47 | |
| 00:51 / 00:52 | |
| 00:57 | |
| 01:01 / 01:02 | |
| 01:05 |
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 |
|---|---|---|---|
| Mon 12 Oct | Uithuizermeeden 01:16Partial coverage | 0 min | — |
| Mon 5 Oct | Uithuizermeeden 01:19 | No data | — |
| Mon 21 Sept | Uithuizermeeden 01:16 | No data | — |
| Mon 14 Sept | Uithuizermeeden 01:16 | No data | — |
| Mon 7 Sept | Uithuizermeeden 01:16 | No data | — |
| Mon 24 Aug | Uithuizermeeden 01:16 | No data | — |
| Mon 17 Aug | Uithuizermeeden 01:16 | No data | — |
| Mon 10 Aug | Uithuizermeeden 01:16 | No data | — |
| Mon 3 Aug | Uithuizermeeden 01:16 | No data | — |
| Mon 27 Jul | Uithuizermeeden 01:16 | No data | — |
| Mon 20 Jul | Uithuizermeeden 01:16 | No data | — |