S11 9444 Solothurn → Oensingen

View line S11

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

S11 9444 Solothurn–Oensingen: final delay under 3 min on 23 of its 23 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:41 −1 min

  1. Solothurn14:16
  2. Solothurn Sternen14:19
  3. Bei den Weihern14:22
  4. Flumenthal14:26
  5. Wiedlisbach14:31
  6. Niederbipp14:37
  7. Oensingen14:41

Next service: tomorrow 14:16 from Solothurn · Sun 22 Nov

Next departure 14:16 tomorrow · Solothurn
On-time · 30 days
100%
23/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 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 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

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

  • Early 14% · 6
  • On time 86% · 37
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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