S11 9432 Solothurn – Oensingen

View line S11

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

✓ Today’s run finished

Today it reached Oensingen at 11:41 0 min

  1. Solothurn11:16
  2. Solothurn Sternen11:19
  3. Bei den Weihern11:22
  4. Flumenthal11:26
  5. Wiedlisbach11:31
  6. Niederbipp11:37
  7. Oensingen11:41

Next service: tomorrow 11:16 from Solothurn · Wed 18 Nov

Next departure 11:16 tomorrow · Solothurn
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 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: +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

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

  • Early 18% · 6
  • On time 82% · 28
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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
11:16+1 min +1 min
11:17≈ +1 min ≈ +1 min
11:19≈ on time ≈ +1 min
11:20≈ on time ≈ +1 min
11:21≈ on time ≈ +1 min
11:22≈ on time ≈ +1 min
11:23≈ on time ≈ +1 min
11:26≈ on time ≈ +1 min
11:28≈ on time ≈ +1 min
11:31≈ on time ≈ +1 min
11:32≈ on time ≈ +1 min
11:33≈ on time ≈ +1 min
11:37≈ on time ≈ +1 min
11:38≈ on time ≈ +1 min
11:41on 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 NovOensingen 11:390 min—
Mon 16 NovOensingen 11:42No data—
Sun 15 NovOensingen 11:390 min—
Sat 14 NovOensingen 11:390 min—
Fri 13 NovNiederbipp 11:39+2 min+2 min
Thu 12 NovOensingen 11:42No data—
Wed 11 NovOensingen 11:390 min—
Tue 10 NovOensingen 11:39+1 min+2 min
Mon 9 NovOensingen 11:42No data—
Sun 8 NovOensingen 11:390 min—
Sat 7 NovOensingen 11:390 min—
Fri 6 NovOensingen 11:390 min+1 min
Thu 5 NovOensingen 11:420 min—
Wed 4 NovOensingen 11:420 min—
Tue 3 NovOensingen 11:430 min—
Mon 2 NovOensingen 11:42No data—
Sun 1 NovOensingen 11:40−1 min—
Sat 31 OctOensingen 11:420 min+3 min
Fri 30 OctOensingen 11:410 min+1 min
Thu 29 OctOensingen 11:42No data—
Wed 28 OctOensingen 11:41+1 min+1 min
Tue 27 OctOensingen 11:430 min+1 min
Mon 26 OctOensingen 11:43No data—
Sun 25 OctOensingen 11:42No data—
Sat 24 OctOensingen 11:43+1 min+3 min
Fri 23 OctOensingen 11:41−1 min+1 min
Thu 22 OctOensingen 11:42No data—
Wed 21 OctOensingen 11:43+1 min+2 min
Tue 20 OctOensingen 11:43+1 min+1 min
Mon 19 OctOensingen 11:42No data—