Train Arriva 20111 Leer(Ostfriesl) – Winschoten

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

✓ Today’s run finished

Today, last fix heading to Bad Nieuweschans at 12:03 No data

  1. Leer(Ostfriesl)11:23
  2. Ihrhove11:29
  3. Weener11:36
  4. Bunde (D)11:40
  5. Bad Nieuweschans11:46
  6. Winschoten11:58

Next service: tomorrow 11:23 from Leer(Ostfriesl) · Sat 7 Nov

Next departure 11:23 tomorrow · Leer(Ostfriesl)
On-time · 30 days
88%
7/8 runs under 3 min
RT coverage: 7 full · 1 partial · 5 no data
On-time · 90 days
88%
7/8 runs under 3 min
RT coverage: 7 full · 1 partial · 5 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 Winschoten, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 10 Oct Max en route +10 min · last fix heading to — +10 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 88% · 7
  • 3–10 min 13% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • — M n=0
  • 100% T n=1
  • 100% W n=1
  • 100% T n=2
  • — F n=0
  • 50% 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, 8 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
11:23on time +2 min
11:29 / 11:30≈ on time ≈ +3 min
11:36≈ on time ≈ +3 min
11:40 / 11:41≈ on time ≈ +3 min
11:46 / 11:49≈ on time ≈ +4 min
11:58on time +4 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 12:03No data—
Thu 5 NovBad Nieuweschans 12:03Partial coverage0 min—
Wed 4 NovBad Nieuweschans 12:190 min+14 min
Tue 3 NovBad Nieuweschans 12:040 min—
Mon 2 NovBad Nieuweschans 12:03No data—
Sun 1 NovGroningen Europapark 12:390 min+2 min
Sat 31 OctGroningen Europapark 12:380 min+3 min
Fri 30 OctBad Nieuweschans 12:03No data—
Thu 29 OctBad Nieuweschans 12:040 min—
Sun 25 OctGroningen Europapark 12:38No data—
Sat 24 OctGroningen Europapark 12:38No data—
Sun 18 Oct— 12:290 min—
Sat 10 Oct— 12:40+10 min+10 min