S11 9183 Oensingen – Wiedlisbach

View line S11

Oensingen 00:35 → Wiedlisbach 00:42 Daily 0 h 07 min · 6 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Wiedlisbach at 00:47 +5 min

  1. Oensingen00:35
  2. Niederbipp Industrie00:36
  3. Niederbipp00:37
  4. Buchli00:38
  5. Oberbipp00:40
  6. Wiedlisbach00:42

Next service: tomorrow 00:35 from Oensingen · Sat 21 Nov

Next departure 00:35 tomorrow · Oensingen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
73/77 runs under 3 min
RT coverage: 64 full · 13 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Wiedlisbach, in minutes. One bar per run.

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

Worst days

  • Mon 21 Sept Max en route +7 min · last fix heading to Niederbipp +5 min
  • Fri 20 Nov Max en route +5 min · last fix heading to Wiedlisbach +5 min
  • Thu 17 Sept Max en route +5 min · last fix heading to Buchli +4 min
  • Wed 9 Sept Max en route +4 min · last fix heading to Buchli +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 95% · 73
  • 3–10 min 5% · 4
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 92% M n=12
  • 100% T n=13
  • 92% W n=12
  • 91% T n=11
  • 89% F n=9
  • 100% S n=8
  • 100% S n=12

Stops and timetable

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

Last 90 days, 77 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
00:35on time +2 min
00:36≈ on time ≈ +3 min
00:37≈ on time ≈ +2 min
00:38≈ on time ≈ +2 min
00:40≈ +1 min ≈ +2 min
00:42+1 min +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 20 NovWiedlisbach 00:48+5 min+5 min
Thu 19 NovUnterzollikofen 18:28+1 min+1 min
Wed 18 NovUnterzollikofen 18:28+1 min+1 min
Tue 17 NovUnterzollikofen 18:28+1 min+1 min
Mon 16 NovUnterzollikofen 18:27+1 min—
Sun 15 NovUnterzollikofen 18:28+1 min+1 min
Sat 14 NovUnterzollikofen 18:27+1 min+1 min
Fri 13 NovUnterzollikofen 18:28+1 min—
Thu 12 NovUnterzollikofen 18:27+1 min—
Wed 11 NovUnterzollikofen 18:28+1 min—
Tue 10 NovUnterzollikofen 18:29+2 min+3 min
Mon 9 NovUnterzollikofen 18:270 min+3 min
Sun 8 NovUnterzollikofen 18:29+3 min+3 min
Sat 7 NovUnterzollikofen 18:28+1 min+1 min
Fri 6 NovUnterzollikofen 18:28+1 min+1 min
Thu 5 NovUnterzollikofen 18:29+2 min+5 min
Wed 4 NovUnterzollikofen 18:28+1 min+8 min
Tue 3 NovUnterzollikofen 18:27+1 min+1 min
Mon 2 NovUnterzollikofen 18:28+1 min+4 min
Sun 1 NovUnterzollikofen 18:28+1 min+1 min
Sat 31 OctUnterzollikofen 18:270 min—
Fri 30 OctUnterzollikofen 18:28+2 min+2 min
Thu 29 OctUnterzollikofen 18:280 min—
Wed 28 OctUnterzollikofen 18:29+2 min+2 min
Tue 27 OctUnterzollikofen 18:270 min+1 min
Mon 26 OctUnterzollikofen 18:28+1 min+4 min
Sun 25 OctUnterzollikofen 18:270 min+2 min
Sat 24 OctUnterzollikofen 18:26−1 min+10 min
Fri 23 OctUnterzollikofen 18:28+1 min+1 min
Thu 22 OctUnterzollikofen 18:270 min+4 min