S11 9408 Wiedlisbach → Oensingen

View line S11

Wiedlisbach 05:31 → Oensingen 05:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 10 min · 6 stops Aare Seeland mobil

S11 9408 Wiedlisbach–Oensingen: final delay under 3 min on 25 of its 26 runs with data in the last 30 days (96%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 17:43 (GMT+1).

✓ Today’s run finished

Today it reached Oensingen at 05:41 0 min

  1. Wiedlisbach05:31
  2. Oberbipp05:32
  3. Buchli05:33
  4. Niederbipp05:37
  5. Niederbipp Industrie05:38
  6. Oensingen05:41

Next service: Monday 05:31 from Wiedlisbach · Mon 23 Nov

Next departure 05:31 Monday · Wiedlisbach
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Oensingen, 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 2 Nov Max en route +6 min · last fix heading to Oensingen +4 min

Distribution · 90 days

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

  • Early 38% · 16
  • On time 60% · 25
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • — S n=0

Stops and timetable

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

Last 90 days, 42 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
05:31on time +1 min
05:32≈ on time ≈ +1 min
05:33≈ on time ≈ +1 min
05:37≈ on time ≈ on time
05:38≈ on time ≈ on time
05:411 min early on time

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
Sat 21 NovOensingen 05:390 min—
Fri 20 NovOensingen 05:39−1 min—
Thu 19 NovOensingen 05:390 min—
Wed 18 NovOensingen 05:43+2 min+3 min
Tue 17 NovOensingen 05:390 min—
Mon 16 NovOensingen 05:390 min—
Sat 14 NovOensingen 05:390 min—
Fri 13 NovOensingen 05:40+1 min—
Thu 12 NovOensingen 05:390 min—
Wed 11 NovOensingen 05:39−1 min—
Tue 10 NovOensingen 05:39−1 min—
Mon 9 NovOensingen 05:390 min—
Sat 7 NovOensingen 05:390 min—
Fri 6 NovOensingen 05:39−1 min—
Thu 5 NovOensingen 05:390 min—
Wed 4 NovOensingen 05:39−1 min—
Tue 3 NovOensingen 05:39−1 min—
Mon 2 NovOensingen 05:47+4 min+6 min
Sat 31 OctOensingen 05:420 min—
Fri 30 OctOensingen 05:420 min—
Thu 29 OctOensingen 05:420 min+1 min
Wed 28 OctOensingen 05:420 min—
Tue 27 OctOensingen 05:420 min+2 min
Mon 26 OctOensingen 05:400 min—
Sat 24 OctOensingen 05:41−1 min—
Fri 23 OctOensingen 05:41−1 min—
Thu 22 OctOensingen 05:41−1 min—
Wed 21 OctOensingen 05:410 min—
Tue 20 OctOensingen 05:400 min—
Mon 19 OctOensingen 05:41−1 min—