Train Arriva 20110 Groningen – Leer(Ostfriesl)

Groningen 08:32 → Leer(Ostfriesl) 09:36 Daily 1 h 04 min · 9 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 08:32 from Groningen · Sat 7 Nov

Next departure 08:32 today · Groningen
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 10 full · 3 partial · 8 no data
On-time · 90 days
94%
15/16 runs under 3 min
RT coverage: 13 full · 3 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

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

  • Sat 24 Oct Max en route +7 min · last fix heading to Winschoten +7 min

Distribution · 90 days

16 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 0% · 0
  • On time 94% · 15
  • 3–10 min 6% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=2
  • 100% W n=2
  • 100% T n=2
  • 100% F n=1
  • 75% S n=4
  • 100% S n=3

Stops and timetable

Timetable of the latest run from the operator’s GTFS (9 stops).

Last 90 days, 16 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.

StopSched.Usually 9 days in 10
08:32on time on time
08:34 / 08:35≈ on time ≈ on time
08:59 / 09:00≈ on time ≈ on time
09:04 / 09:05≈ on time ≈ on time
09:13 / 09:14≈ on time ≈ on time
09:17 / 09:18≈ on time ≈ on time
09:22 / 09:23≈ on time ≈ +1 min
09:29≈ on time ≈ +1 min
09:36on 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

DateLast stopFinalMax
Fri 6 Nov— 09:22No data—
Mon 2 Nov— 09:19No data—
Sun 1 NovBad Nieuweschans 09:32Partial coverage+2 min+2 min
Sat 31 OctBad Nieuweschans 09:290 min—
Fri 30 OctBad Nieuweschans 09:29No data—
Thu 29 OctBad Nieuweschans 09:290 min—
Wed 28 OctBad Nieuweschans 09:320 min—
Tue 27 OctBad Nieuweschans 09:280 min—
Mon 26 OctBad Nieuweschans 09:290 min—
Sun 25 OctWinschoten 09:19No data—
Sat 24 OctWinschoten 09:24+7 min+7 min
Sun 18 OctBad Nieuweschans 09:28Partial coverage0 min—
Sat 17 OctBad Nieuweschans 09:290 min—
Fri 16 OctBad Nieuweschans 09:29No data—
Thu 15 OctBad Nieuweschans 09:28No data—
Wed 14 OctBad Nieuweschans 09:29No data—
Tue 13 OctBad Nieuweschans 09:28No data—
Mon 12 OctWinschoten 10:240 min—
Sun 11 OctBad Nieuweschans 09:31Partial coverage+1 min+1 min
Sat 10 OctBad Nieuweschans 09:570 min+25 min
Fri 9 OctBad Nieuweschans 09:330 min+3 min
Thu 8 OctBad Nieuweschans 09:30+1 min—
Wed 7 OctBad Nieuweschans 09:280 min—
Tue 6 OctBad Nieuweschans 09:290 min—
Mon 5 OctBad Nieuweschans 09:30No data—