Train Arriva 20113 Leer(Ostfriesl) – Winschoten

Leer(Ostfriesl) 12:23 → Winschoten 12:58 Daily 0 h 35 min · 6 stops Arriva

It has not run yet today

Last recorded run: Friday 6 November No data

Next service: today 12:23 from Leer(Ostfriesl) · Sat 7 Nov

Next departure 12:23 today · Leer(Ostfriesl)
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 6 full · 1 partial · 5 no data
On-time · 90 days
100%
10/10 runs under 3 min
RT coverage: 9 full · 1 partial · 5 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: 0 min

Last 30 days

Arrival delay at Winschoten, 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

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

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

On-time by weekday

  • 100% M n=3
  • 100% T n=1
  • 100% W n=2
  • 100% T n=1
  • — F n=0
  • 100% S n=2
  • 100% S n=1

Stops and timetable

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

Last 90 days, 10 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
12:23on time on time
12:29 / 12:30≈ on time ≈ on time
12:36≈ on time ≈ +1 min
12:40 / 12:41≈ on time ≈ +1 min
12:46 / 12:49≈ on time ≈ +1 min
12:58on 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 NovBad Nieuweschans 13:03No data—
Thu 5 NovBad Nieuweschans 13:03Partial coverage0 min—
Wed 4 NovBad Nieuweschans 13:130 min+9 min
Tue 3 NovBad Nieuweschans 13:09No data—
Mon 2 NovBad Nieuweschans 13:030 min—
Sun 1 NovGroningen Europapark 13:40+1 min+5 min
Sat 31 OctGroningen Europapark 13:380 min—
Fri 30 OctBad Nieuweschans 13:03No data—
Thu 29 OctBad Nieuweschans 13:03No data—
Mon 26 Oct— 13:010 min—
Sun 25 OctGroningen Europapark 13:38No data—
Sat 24 OctGroningen Europapark 13:380 min—
Wed 7 Oct— 13:03+3 min+3 min
Tue 6 Oct— 13:000 min—
Mon 5 Oct— 13:000 min—