Train Arriva 20134 Groningen – Leer(Ostfriesl)

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

It has not run yet today

Last recorded run: Sunday 15 November +2 min

Next service: today 20:32 from Groningen · Mon 16 Nov

Next departure 20:32 today · Groningen
On-time · 30 days
100%
8/8 runs under 3 min
RT coverage: 8 full · 0 partial · 2 no data
On-time · 90 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 13
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=1
  • 100% W n=2
  • — T n=0
  • — F n=0
  • 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, 13 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
20:32on time on time
20:34 / 20:35≈ on time ≈ on time
20:59 / 21:00≈ on time ≈ +1 min
21:04 / 21:05≈ on time ≈ +1 min
21:13 / 21:14≈ on time ≈ +1 min
21:17 / 21:18≈ on time ≈ +1 min
21:22 / 21:23≈ on time ≈ +1 min
21:29≈ on time ≈ +1 min
21: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
Sun 15 Nov— 21:24+2 min+3 min
Wed 11 Nov— 21:19+1 min—
Sun 8 NovWinschoten 21:52+1 min+1 min
Sat 7 NovWinschoten 21:19+1 min+1 min
Sun 1 NovWinschoten 21:190 min—
Sat 31 OctWinschoten 21:190 min—
Mon 26 Oct— 21:480 min—
Sun 25 OctWinschoten 21:20No data—
Sat 24 OctWinschoten 21:19No data—
Sun 18 OctBad Nieuweschans 21:290 min—
Sat 17 OctBad Nieuweschans 21:28No data—
Sun 11 OctWinschoten 21:190 min—
Sat 10 OctBad Nieuweschans 21:280 min—
Wed 7 Oct— 21:220 min—
Tue 6 Oct— 21:26+1 min+1 min
Mon 5 Oct— 22:070 min—