Train Arriva 20108 Winschoten – Leer(Ostfriesl)

Winschoten 08:05 → Leer(Ostfriesl) 08:36 Daily 0 h 31 min · 6 stops Arriva

It has not run yet today

Last recorded run: Monday 9 November +3 min

Next service: tomorrow 08:05 from Winschoten · Wed 11 Nov

Next departure 08:05 tomorrow · Winschoten
On-time · 30 days
92%
12/13 runs under 3 min
RT coverage: 13 full · 0 partial · 6 no data
On-time · 90 days
95%
18/19 runs under 3 min
RT coverage: 19 full · 0 partial · 7 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: +3 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

  • Sun 8 Nov Max en route +3 min · last fix heading to Winschoten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 18
  • 3–10 min 5% · 1
  • 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
  • 100% T n=2
  • 100% F n=1
  • 100% S n=5
  • 75% S n=4

Stops and timetable

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

Last 90 days, 19 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:05on time on time
08:13 / 08:14≈ on time ≈ +1 min
08:17 / 08:18≈ on time ≈ +1 min
08:22 / 08:23≈ on time ≈ +2 min
08:29≈ on time ≈ +2 min
08: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
Mon 9 Nov— 08:24+3 min+3 min
Sun 8 NovWinschoten 08:19+3 min+3 min
Sat 7 NovWinschoten 08:19+2 min+2 min
Sun 1 NovBad Nieuweschans 08:290 min—
Sat 31 OctBad Nieuweschans 08:280 min—
Fri 30 OctBad Nieuweschans 08:30No data—
Thu 29 OctBad Nieuweschans 08:280 min—
Wed 28 OctBad Nieuweschans 08:290 min—
Tue 27 OctBad Nieuweschans 08:290 min—
Mon 26 OctBad Nieuweschans 08:340 min—
Sun 25 OctWinschoten 08:19No data—
Sat 24 OctWinschoten 08:19+1 min+1 min
Sun 18 OctBad Nieuweschans 08:280 min—
Sat 17 OctBad Nieuweschans 08:280 min—
Fri 16 OctBad Nieuweschans 08:29No data—
Thu 15 OctBad Nieuweschans 08:28No data—
Wed 14 OctBad Nieuweschans 08:28No data—
Tue 13 OctBad Nieuweschans 08:28No data—
Mon 12 OctBad Nieuweschans 08:280 min—
Sun 11 OctBad Nieuweschans 08:280 min—
Sat 10 OctBad Nieuweschans 08:32+3 min+3 min
Fri 9 OctBad Nieuweschans 08:290 min—
Thu 8 OctBad Nieuweschans 08:30+1 min—
Wed 7 OctBad Nieuweschans 08:290 min—
Tue 6 OctBad Nieuweschans 08:280 min—
Mon 5 OctBad Nieuweschans 08:29No data—