S11 9442 Solothurn → Oensingen

View line S11

Solothurn 13:46 → Oensingen 14:11 Daily 0 h 25 min · 15 stops Aare Seeland mobil

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

✓ Today’s run finished

Today it reached Oensingen at 14:11 0 min

  1. Solothurn13:46
  2. Solothurn Sternen13:49
  3. Bei den Weihern13:52
  4. Flumenthal13:56
  5. Wiedlisbach14:01
  6. Niederbipp14:07
  7. Oensingen14:11

Next service: tomorrow 13:46 from Solothurn · Sun 22 Nov

Next departure 13:46 tomorrow · Solothurn
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
38/38 runs under 3 min
RT coverage: 38 full · 0 partial · 11 no data
Typical delay
−1min
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 Oensingen, 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

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

  • Early 39% · 15
  • On time 61% · 23
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=2
  • 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, 38 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
13:46+1 min +1 min
13:47≈ +1 min ≈ +1 min
13:49≈ on time ≈ +1 min
13:50≈ on time ≈ +1 min
13:51≈ on time ≈ +1 min
13:52≈ on time ≈ +1 min
13:53≈ on time ≈ +1 min
13:56≈ on time ≈ +1 min
13:58≈ on time ≈ +1 min
14:01≈ on time ≈ +1 min
14:02≈ on time ≈ +1 min
14:03≈ on time ≈ +1 min
14:07≈ on time ≈ +1 min
14:08≈ on time ≈ +1 min
14:111 min early +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 NovOensingen 14:090 min+1 min
Fri 20 NovOensingen 14:13+1 min+2 min
Thu 19 NovOensingen 14:12No data—
Wed 18 NovOensingen 14:13+1 min+1 min
Tue 17 NovOensingen 14:090 min—
Mon 16 NovOensingen 14:12No data—
Sun 15 NovOensingen 14:090 min—
Sat 14 NovOensingen 14:12+1 min+3 min
Fri 13 NovOensingen 14:090 min+1 min
Thu 12 NovOensingen 14:12No data—
Wed 11 NovOensingen 14:09+1 min+2 min
Tue 10 NovOensingen 14:09+1 min—
Mon 9 NovOensingen 14:12No data—
Sun 8 NovOensingen 14:090 min—
Sat 7 NovOensingen 14:090 min—
Fri 6 NovOensingen 14:09+1 min—
Thu 5 NovOensingen 14:12No data—
Wed 4 NovOensingen 14:090 min—
Tue 3 NovOensingen 14:090 min—
Mon 2 NovOensingen 14:12No data—
Sun 1 NovOensingen 14:10−2 min—
Sat 31 OctOensingen 14:10−2 min—
Fri 30 OctOensingen 14:11−1 min—
Thu 29 OctOensingen 14:12No data—
Wed 28 OctOensingen 14:11−1 min—
Tue 27 OctOensingen 14:14+2 min+4 min
Mon 26 OctOensingen 14:12No data—
Sun 25 OctOensingen 14:10−2 min+1 min
Sat 24 OctOensingen 14:11−1 min+3 min
Fri 23 OctOensingen 14:11−1 min+1 min