S11 9430 Solothurn → Oensingen

View line S11

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

S11 9430 Solothurn–Oensingen: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 14:54 (GMT+1).

✓ Today’s run finished

Today it reached Oensingen at 11:11 0 min

  1. Solothurn10:46
  2. Solothurn Sternen10:49
  3. Bei den Weihern10:52
  4. Flumenthal10:56
  5. Wiedlisbach11:01
  6. Niederbipp11:07
  7. Oensingen11:11

Next service: tomorrow 10:46 from Solothurn · Sun 22 Nov

Next departure 10:46 tomorrow · Solothurn
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
98%
46/47 runs under 3 min
RT coverage: 47 full · 0 partial · 2 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: +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

Worst days

  • Sat 10 Oct Max en route +5 min · last fix heading to Oensingen +4 min

Distribution · 90 days

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

  • Early 21% · 10
  • On time 77% · 36
  • 3–10 min 2% · 1
  • 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=5
  • 100% F n=7
  • 86% S n=7
  • 100% S n=7

Stops and timetable

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

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