S11 9425 Oensingen → Solothurn

View line S11

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

S11 9425 Oensingen–Solothurn: final delay under 3 min on 28 of its 28 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 14:51 (GMT+1).

✓ Today’s run finished

Today it reached Solothurn at 10:42 −1 min

  1. Oensingen10:17
  2. Niederbipp10:19
  3. Wiedlisbach10:24
  4. Flumenthal10:29
  5. Bei den Weihern10:32
  6. Solothurn Sternen10:37
  7. Solothurn10:42

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

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

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

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

On-time by weekday

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