S11 9412 Solothurn – Oensingen

View line S11

Solothurn 06:16 → Oensingen 06:41 Mon, Tue, Wed, Thu, Fri, Sat 0 h 25 min · 15 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Oensingen at 06:43 +2 min

  1. Solothurn06:16
  2. Solothurn Sternen06:19
  3. Bei den Weihern06:22
  4. Flumenthal06:26
  5. Wiedlisbach06:31
  6. Niederbipp06:37
  7. Oensingen06:41

Next service: tomorrow 06:16 from Solothurn · Tue 17 Nov

Next departure 06:16 tomorrow · Solothurn
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
97%
36/37 runs under 3 min
RT coverage: 37 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
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

  • Mon 12 Oct Max en route +5 min · last fix heading to Oensingen +5 min

Distribution · 90 days

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

  • Early 11% · 4
  • On time 86% · 32
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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