Train Arriva 37356 Leeuwarden → Groningen Europapark
Arriva 37356 Leeuwarden–Groningen Europapark: final delay under 3 min on 20 of its 21 runs with data in the last 30 days (95%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 06:41 (GMT+1).
An alert on this phone or computer when the 37356 is 5 min or more late, every day it runs. No account, no email.
It has not run yet today
Last recorded run: Saturday 21 November 0 min
Next service: today 15:16 from Leeuwarden · Sun 22 Nov
Last 30 days
Arrival delay at Groningen Europapark, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Thu 8 Oct Max en route +4 min · last fix heading to Groningen +3 min
- Sun 8 Nov Max en route +4 min · last fix heading to Groningen +3 min
Distribution · 90 days
32 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 94% · 30
- 3–10 min 6% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=5
- 67% T n=3
- 100% F n=3
- 100% S n=6
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (5 stops).
Last 90 days, 32 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 |
|---|---|---|---|
| 15:16 | on time | on time | |
| 15:25 | ≈ on time | ≈ +1 min | |
| 15:41 | ≈ on time | ≈ +2 min | |
| 15:51 / 15:52 | ≈ on time | ≈ +2 min | |
| 15:55 | on time | +3 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 |
|---|---|---|---|
| Sat 21 Nov | Groningen 16:04Partial coverage | 0 min | +1 min |
| Fri 20 Nov | Groningen 16:04 | 0 min | +1 min |
| Thu 19 Nov | Groningen 16:14 | 0 min | +7 min |
| Wed 18 Nov | Groningen 16:07 | +1 min | +2 min |
| Tue 17 Nov | Groningen 16:09 | +3 min | +3 min |
| Mon 16 Nov | Groningen 16:09 | 0 min | +1 min |
| Sun 15 Nov | Groningen 16:08 | 0 min | — |
| Sat 14 Nov | Groningen 16:04Partial coverage | 0 min | +1 min |
| Fri 13 Nov | Groningen 16:09 | 0 min | +3 min |
| Thu 12 Nov | Groningen 16:04 | +1 min | +1 min |
| Wed 11 Nov | Groningen 16:08 | +2 min | +2 min |
| Tue 10 Nov | Groningen 16:04 | 0 min | +1 min |
| Mon 9 Nov | Groningen 16:04 | 0 min | — |
| Sun 8 Nov | Groningen 16:12 | +3 min | +4 min |
| Sat 7 Nov | Groningen 16:04Partial coverage | 0 min | — |
| Fri 6 Nov | Groningen 16:14 | No data | — |
| Thu 5 Nov | Groningen 16:10 | No data | — |
| Wed 4 Nov | Groningen 16:04 | 0 min | +1 min |
| Tue 3 Nov | Groningen 16:07 | No data | — |
| Mon 2 Nov | Groningen 16:12 | No data | — |
| Sun 1 Nov | Groningen 16:12 | +2 min | +2 min |
| Sat 31 Oct | Groningen 16:06Partial coverage | 0 min | +1 min |
| Fri 30 Oct | Groningen 16:07 | No data | — |
| Thu 29 Oct | Groningen 16:07 | No data | — |
| Wed 28 Oct | Groningen 16:06 | 0 min | — |
| Tue 27 Oct | Groningen 16:07 | 0 min | — |
| Mon 26 Oct | Groningen 16:06 | No data | — |
| Sun 25 Oct | Groningen 16:08 | No data | — |
| Sat 24 Oct | Groningen 16:07Partial coverage | +1 min | +1 min |
| Fri 23 Oct | Groningen 16:07 | No data | — |