S11 9441 Oensingen – Solothurn

View line S11

Oensingen 14:17 → Solothurn 14:42 Daily 0 h 25 min · 15 stops Aare Seeland mobil

✓ Today’s run finished

Today, last fix heading to Solothurn at 14:44 No data

  1. Oensingen14:17
  2. Niederbipp14:19
  3. Wiedlisbach14:24
  4. Flumenthal14:29
  5. Bei den Weihern14:32
  6. Solothurn Sternen14:37
  7. Solothurn14:42

Next service: tomorrow 14:17 from Oensingen · Fri 13 Nov

Next departure 14:17 tomorrow · Oensingen
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
97%
33/34 runs under 3 min
RT coverage: 34 full · 0 partial · 10 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 Solothurn, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Fri 9 Oct Max en route +4 min · last fix heading to Solothurn +3 min

Distribution · 90 days

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

  • Early 32% · 11
  • On time 65% · 22
  • 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=6
  • 100% W n=7
  • 100% T n=2
  • 80% F n=5
  • 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, 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
14:17on time on time
14:18≈ on time ≈ on time
14:19≈ on time ≈ on time
14:20≈ on time ≈ on time
14:22≈ on time ≈ on time
14:24≈ on time ≈ on time
14:27≈ on time ≈ +1 min
14:29≈ on time ≈ +1 min
14:31≈ on time ≈ +1 min
14:32≈ on time ≈ +1 min
14:35≈ on time ≈ +1 min
14:36≈ on time ≈ +1 min
14:37≈ on time ≈ +1 min
14:38≈ on time ≈ +1 min
14:42on 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
Thu 12 NovSolothurn 14:44No data—
Wed 11 NovSolothurn 14:42−1 min—
Tue 10 NovSolothurn 14:420 min—
Mon 9 NovSolothurn 14:43No data—
Sun 8 NovSolothurn 14:420 min—
Sat 7 NovSolothurn 14:42−1 min—
Fri 6 NovSolothurn 14:43+2 min+2 min
Thu 5 NovSolothurn 14:43No data—
Wed 4 NovSolothurn 14:420 min—
Tue 3 NovSolothurn 14:42−1 min+1 min
Mon 2 NovSolothurn 14:43No data—
Sun 1 NovSolothurn 14:420 min—
Sat 31 OctSolothurn 14:43+1 min—
Fri 30 OctSolothurn 14:420 min—
Thu 29 OctSolothurn 14:43No data—
Wed 28 OctSolothurn 14:430 min—
Tue 27 OctSolothurn 14:430 min—
Mon 26 OctSolothurn 14:43No data—
Sun 25 OctSolothurn 14:42−1 min—
Sat 24 OctSolothurn 14:43+1 min+1 min
Fri 23 OctSolothurn 14:44+1 min—
Thu 22 OctSolothurn 14:43No data—
Wed 21 OctSolothurn 14:430 min—
Tue 20 OctSolothurn 14:44+1 min+2 min
Mon 19 OctSolothurn 14:43No data—
Sun 18 OctSolothurn 14:41−1 min—
Sat 17 OctSolothurn 14:430 min+1 min
Fri 16 OctSolothurn 14:42−2 min—
Thu 15 OctSolothurn 14:43No data—
Wed 14 OctSolothurn 14:42−1 min—