S11 9417 Oensingen → Solothurn

View line S11

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

S11 9417 Oensingen–Solothurn: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 16:33 (GMT+1).

✓ Today’s run finished

Today it reached Solothurn at 08:42 −1 min

  1. Oensingen08:17
  2. Niederbipp08:19
  3. Wiedlisbach08:24
  4. Flumenthal08:29
  5. Bei den Weihern08:32
  6. Solothurn Sternen08:37
  7. Solothurn08:42

Next service: tomorrow 08:17 from Oensingen · Sun 22 Nov

Next departure 08:17 tomorrow · Oensingen
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
52/53 runs under 3 min
RT coverage: 53 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Mon 16 Nov Max en route +3 min · last fix heading to Solothurn +3 min

Distribution · 90 days

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

  • Early 17% · 9
  • On time 81% · 43
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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