S11 9470 Solothurn – Oensingen

View line S11

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

Running now · updated 20:55

Position estimated from the timetable

Between Riedholz and Flumenthal No data

Estimated arrival at Oensingen 21:11 · 42 km/h

  1. Solothurn20:46
  2. Solothurn Sternen20:49
  3. Bei den Weihern20:52
  4. Riedholz20:53
  5. Flumenthal20:56
  6. Wiedlisbach21:01
  7. Oensingen21:11
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 no data
Typical delay
−1min
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 Oensingen, 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

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

  • Early 43% · 20
  • On time 57% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=6
  • 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, 46 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
20:46+1 min +1 minPassed
20:47≈ +1 min ≈ +1 minPassed
20:49≈ on time ≈ +1 minPassed
20:50≈ on time ≈ +1 minPassed
20:51≈ on time ≈ +1 minPassed
20:52≈ on time ≈ +1 minPassed
20:53≈ on time ≈ +1 minPassed
20:56≈ on time ≈ +1 minNext
20:58≈ on time ≈ +1 min
21:01≈ on time ≈ +1 min
21:02≈ on time ≈ +1 min
21:03≈ on time ≈ +1 min
21:07≈ on time ≈ +1 min
21:08≈ on time ≈ +1 min
21:111 min early +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
Thu 19 NovFlumenthal 20:54Partial coverageNo data—
Wed 18 NovOensingen 21:09−1 min+2 min
Tue 17 NovOensingen 21:090 min—
Mon 16 NovOensingen 21:09+1 min—
Sun 15 NovOensingen 21:090 min+1 min
Sat 14 NovOensingen 21:13+1 min+1 min
Fri 13 NovOensingen 21:12−1 min—
Thu 12 NovOensingen 21:13+1 min+2 min
Wed 11 NovOensingen 21:09+1 min+2 min
Tue 10 NovOensingen 21:080 min+1 min
Mon 9 NovOensingen 21:090 min—
Sun 8 NovOensingen 21:090 min—
Sat 7 NovOensingen 21:09−2 min—
Fri 6 NovOensingen 21:090 min+1 min
Thu 5 NovOensingen 21:09−1 min—
Wed 4 NovOensingen 21:090 min—
Tue 3 NovOensingen 21:130 min—
Mon 2 NovOensingen 21:130 min—
Sun 1 NovOensingen 21:090 min—
Sat 31 OctOensingen 21:10−2 min+1 min
Fri 30 OctOensingen 21:10−1 min—
Thu 29 OctOensingen 21:11−1 min—
Wed 28 OctOensingen 21:11−1 min+1 min
Tue 27 OctOensingen 21:11−2 min—
Mon 26 OctOensingen 21:110 min—
Sun 25 OctOensingen 21:120 min+2 min
Sat 24 OctOensingen 21:11−1 min—
Fri 23 OctOensingen 21:10−2 min—
Thu 22 OctOensingen 21:10−2 min—
Wed 21 OctOensingen 21:110 min+1 min