S11 9434 Solothurn – Oensingen

View line S11

Solothurn 11:46 → Oensingen 12:11 Daily 0 h 25 min · 15 stops Aare Seeland mobil

Running now · updated 12:04

Position estimated from the timetable

Between Oberbipp and Buchli +1 min

Estimated arrival at Oensingen 12:12 12:11 · 84 km/h

  1. Solothurn11:46
  2. Solothurn Sternen11:49
  3. Bei den Weihern11:52
  4. Flumenthal11:56
  5. Oberbipp12:02
  6. Buchli12:03
  7. Oensingen12:11

Today it is running worse than usual: typical arrival delay is 0 min; 100% of the last 21 runs arrived on time.

On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 20 full · 1 partial · 9 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 33 full · 1 partial · 11 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: +2 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

  • Wed 14 Oct Max en route +4 min · last fix heading to Oensingen +3 min

Distribution · 90 days

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

  • Early 29% · 10
  • On time 68% · 23
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 83% W n=6
  • 100% T n=1
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 33 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 10Today
11:46+1 min +1 minPassed
11:47≈ +1 min ≈ +1 minPassed
11:49≈ +1 min ≈ +1 minPassed
11:50≈ +1 min ≈ +1 minPassed
11:51≈ +1 min ≈ +1 minPassed
11:52≈ +1 min ≈ +1 minPassed
11:53≈ on time ≈ +1 minPassed
11:56≈ on time ≈ +1 minPassed
11:58≈ on time ≈ +1 minPassed
12:01≈ on time ≈ +1 minPassed
12:02≈ on time ≈ +1 minPassed
12:03≈ on time ≈ +1 minNext
12:07≈ on time ≈ +1 min
12:08≈ on time ≈ +1 min
12:11on 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
Tue 17 NovWiedlisbach 11:59Partial coverage+1 min+1 min
Mon 16 NovOensingen 12:12No data—
Sun 15 NovOensingen 12:090 min—
Sat 14 NovOensingen 12:090 min—
Fri 13 NovOensingen 12:090 min—
Thu 12 NovOensingen 12:12No data—
Wed 11 NovOensingen 12:090 min—
Tue 10 NovOensingen 12:090 min+1 min
Mon 9 NovOensingen 12:12No data—
Sun 8 NovOensingen 12:090 min—
Sat 7 NovOensingen 12:090 min+1 min
Fri 6 NovOensingen 12:09+1 min—
Thu 5 NovOensingen 12:12No data—
Wed 4 NovNiederbipp Industrie 12:09+1 min+2 min
Tue 3 NovOensingen 12:090 min—
Mon 2 NovOensingen 12:12No data—
Sun 1 NovOensingen 12:11−1 min+1 min
Sat 31 OctOensingen 12:13+2 min+2 min
Fri 30 OctOensingen 12:14+2 min+3 min
Thu 29 OctOensingen 12:12No data—
Wed 28 OctOensingen 12:110 min+1 min
Tue 27 OctOensingen 12:13+1 min+2 min
Mon 26 OctOensingen 12:13No data—
Sun 25 OctOensingen 12:10−2 min+1 min
Sat 24 OctOensingen 12:10−2 min+1 min
Fri 23 OctOensingen 12:120 min+2 min
Thu 22 OctOensingen 12:12No data—
Wed 21 OctOensingen 12:14+2 min+3 min
Tue 20 OctOensingen 12:12−1 min+1 min
Mon 19 OctOensingen 12:12No data—