S11 9447 Oensingen – Solothurn

View line S11

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

✓ Today’s run finished

Today it reached Solothurn at 16:12 0 min

  1. Oensingen15:47
  2. Niederbipp15:49
  3. Wiedlisbach15:54
  4. Flumenthal15:59
  5. Bei den Weihern16:02
  6. Solothurn Sternen16:07
  7. Solothurn16:12

Next service: tomorrow 15:47 from Oensingen · Wed 18 Nov

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

Distribution · 90 days

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

  • Early 28% · 13
  • On time 72% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=7
  • 100% W n=6
  • 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 10
15:47on time on time
15:48≈ on time ≈ on time
15:49≈ on time ≈ on time
15:50≈ on time ≈ on time
15:52≈ on time ≈ on time
15:54≈ on time ≈ on time
15:57≈ on time ≈ on time
15:59≈ on time ≈ +1 min
16:01≈ on time ≈ +1 min
16:02≈ on time ≈ +1 min
16:05≈ on time ≈ +1 min
16:06≈ on time ≈ +1 min
16:07≈ on time ≈ +1 min
16:08≈ on time ≈ +1 min
16:12on 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 NovSolothurn 16:140 min—
Mon 16 NovSolothurn 16:12+1 min—
Sun 15 NovSolothurn 16:12−1 min—
Sat 14 NovSolothurn 16:090 min—
Fri 13 NovSolothurn 16:130 min—
Thu 12 NovSolothurn 16:13+1 min+1 min
Wed 11 NovSolothurn 16:130 min—
Tue 10 NovSolothurn 16:12−1 min—
Mon 9 NovSolothurn 16:13+1 min—
Sun 8 NovSolothurn 16:12−1 min—
Sat 7 NovSolothurn 16:090 min—
Fri 6 NovSolothurn 16:130 min—
Thu 5 NovSolothurn 16:12−2 min—
Wed 4 NovSolothurn 16:14+1 min—
Tue 3 NovSolothurn 16:13+1 min—
Mon 2 NovSolothurn 16:14+2 min+2 min
Sun 1 NovSolothurn 16:12−1 min—
Sat 31 OctSolothurn 16:120 min—
Fri 30 OctSolothurn 16:13+1 min—
Thu 29 OctSolothurn 16:12−1 min—
Wed 28 OctSolothurn 16:140 min—
Tue 27 OctSolothurn 16:14+1 min+1 min
Mon 26 OctSolothurn 16:120 min—
Sun 25 OctSolothurn 16:14+1 min+2 min
Sat 24 OctSolothurn 16:12−1 min—
Fri 23 OctSolothurn 16:15+1 min+2 min
Thu 22 OctSolothurn 16:15+2 min+2 min
Wed 21 OctSolothurn 16:13+1 min—
Tue 20 OctSolothurn 16:12−1 min—
Mon 19 OctSolothurn 16:12−1 min—