Train Arriva 20126 Winschoten – Leer(Ostfriesl)

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

It has not run yet today

Last recorded run: Monday 2 November 0 min

Next service: today 17:05 from Winschoten · Thu 5 Nov

Next departure 17:05 today · Winschoten
On-time · 30 days
100%
13/13 runs under 3 min
RT coverage: 13 full · 0 partial · 9 no data
On-time · 90 days
100%
14/14 runs under 3 min
RT coverage: 14 full · 0 partial · 10 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: +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

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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