Train Arriva 20122 Groningen – Leer(Ostfriesl)

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

It has not run yet today

Last recorded run: Sunday 15 November 0 min

Next service: today 14:32 from Groningen · Thu 19 Nov

Next departure 14:32 today · Groningen
On-time · 30 days
100%
11/11 runs under 3 min
RT coverage: 11 full · 0 partial · 4 no data
On-time · 90 days
90%
18/20 runs under 3 min
RT coverage: 20 full · 0 partial · 9 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +1 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

  • Fri 9 Oct Max en route +8 min · last fix heading to Bad Nieuweschans +8 min
  • Mon 5 Oct Max en route +7 min · last fix heading to Bad Nieuweschans +7 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 18
  • 3–10 min 10% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 20 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
14:32on time +1 min
14:34 / 14:35≈ on time ≈ +1 min
14:59 / 15:00≈ on time ≈ +2 min
15:04 / 15:05≈ on time ≈ +2 min
15:13 / 15:14≈ on time ≈ +2 min
15:17 / 15:18≈ on time ≈ +2 min
15:22 / 15:23≈ on time ≈ +2 min
15:29≈ on time ≈ +2 min
15:36on 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

DateLast stopFinalMax
Sun 15 Nov— 15:140 min—
Wed 11 Nov— 15:190 min—
Sun 8 NovWinschoten 15:19+1 min+1 min
Sat 7 NovWinschoten 15:19+1 min+1 min
Thu 5 Nov— 15:19No data—
Mon 2 Nov— 15:190 min—
Sun 1 NovBad Nieuweschans 15:300 min—
Sat 31 OctBad Nieuweschans 15:30+1 min+1 min
Fri 30 OctBad Nieuweschans 15:30No data—
Thu 29 OctBad Nieuweschans 15:290 min—
Wed 28 OctBad Nieuweschans 15:280 min—
Tue 27 OctBad Nieuweschans 15:280 min—
Mon 26 OctBad Nieuweschans 15:280 min—
Sun 25 OctWinschoten 15:19No data—
Sat 24 OctWinschoten 15:19No data—
Sun 18 OctBad Nieuweschans 15:30+1 min—
Sat 17 OctBad Nieuweschans 15:29No data—
Fri 16 OctBad Nieuweschans 15:30No data—
Thu 15 OctBad Nieuweschans 15:28No data—
Wed 14 OctBad Nieuweschans 15:29No data—
Tue 13 OctBad Nieuweschans 15:30No data—
Mon 12 OctBad Nieuweschans 15:280 min—
Sun 11 OctBad Nieuweschans 15:330 min—
Sat 10 OctWinschoten 15:320 min—
Fri 9 OctBad Nieuweschans 15:37+8 min+8 min
Thu 8 OctBad Nieuweschans 15:31+2 min+2 min
Wed 7 OctBad Nieuweschans 15:31+2 min+2 min
Tue 6 OctBad Nieuweschans 15:280 min—
Mon 5 OctBad Nieuweschans 15:36+7 min+7 min