Train Arriva 20124 Groningen – Leer(Ostfriesl)
It has not run yet today
Last recorded run: Sunday 1 November +1 min
Next service: tomorrow 15:32 from Groningen · Sat 7 Nov
Last 30 days
Arrival delay at Leer(Ostfriesl), 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 +6 min · last fix heading to Bad Nieuweschans +6 min
- Sat 10 Oct Max en route +6 min · last fix heading to Bad Nieuweschans +6 min
- Fri 9 Oct Max en route +4 min · last fix heading to Bad Nieuweschans +4 min
Distribution · 90 days
15 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 80% · 12
- 3–10 min 20% · 3
- 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
- 50% T n=2
- 0% F n=1
- 50% S n=2
- 100% S n=3
Stops and timetable
Timetable of the latest run from the operator’s GTFS (9 stops).
Last 90 days, 15 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:32 | on time | on time | |
| 15:34 / 15:35 | ≈ on time | ≈ on time | |
| 15:59 / 16:00 | ≈ on time | ≈ +2 min | |
| 16:04 / 16:05 | ≈ on time | ≈ +3 min | |
| 16:13 / 16:14 | ≈ on time | ≈ +4 min | |
| 16:17 / 16:18 | ≈ on time | ≈ +4 min | |
| 16:22 / 16:23 | ≈ on time | ≈ +4 min | |
| 16:29 | ≈ on time | ≈ +5 min | |
| 16:36 | on time | +5 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 |
|---|---|---|---|
| Sun 1 Nov | Bad Nieuweschans 16:31Partial coverage | +1 min | +1 min |
| Sat 31 Oct | Bad Nieuweschans 16:31 | +2 min | +2 min |
| Fri 30 Oct | Bad Nieuweschans 16:29 | No data | — |
| Thu 29 Oct | Bad Nieuweschans 16:28 | 0 min | — |
| Wed 28 Oct | Bad Nieuweschans 16:28 | 0 min | — |
| Tue 27 Oct | Bad Nieuweschans 16:28 | 0 min | — |
| Mon 26 Oct | Bad Nieuweschans 16:29 | 0 min | — |
| Sun 25 Oct | Winschoten 16:19 | No data | — |
| Sat 24 Oct | Winschoten 16:19 | No data | — |
| Sun 18 Oct | Bad Nieuweschans 16:30Partial coverage | +1 min | +1 min |
| Sat 17 Oct | Bad Nieuweschans 16:28 | No data | — |
| Fri 16 Oct | Bad Nieuweschans 16:30 | No data | — |
| Thu 15 Oct | Bad Nieuweschans 16:29 | No data | — |
| Wed 14 Oct | Bad Nieuweschans 16:29 | No data | — |
| Tue 13 Oct | Bad Nieuweschans 16:29 | No data | — |
| Mon 12 Oct | Bad Nieuweschans 16:28 | 0 min | — |
| Sun 11 Oct | Bad Nieuweschans 16:28Partial coverage | 0 min | — |
| Sat 10 Oct | Bad Nieuweschans 16:35 | +6 min | +6 min |
| Fri 9 Oct | Bad Nieuweschans 16:33 | +4 min | +4 min |
| Thu 8 Oct | Bad Nieuweschans 16:35 | +6 min | +6 min |
| Wed 7 Oct | Bad Nieuweschans 16:29 | 0 min | — |
| Tue 6 Oct | Bad Nieuweschans 16:29 | 0 min | — |
| Mon 5 Oct | Bad Nieuweschans 16:28 | 0 min | +3 min |