S11 9440 Solothurn – Oensingen

View line S11

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

✓ Today’s run finished

Today it reached Oensingen at 13:42 +1 min

  1. Solothurn13:16
  2. Solothurn Sternen13:19
  3. Bei den Weihern13:22
  4. Flumenthal13:26
  5. Wiedlisbach13:31
  6. Niederbipp13:37
  7. Oensingen13:41

Next service: tomorrow 13:16 from Solothurn · Mon 9 Nov

Next departure 13:16 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
97%
31/32 runs under 3 min
RT coverage: 32 full · 0 partial · 8 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

Worst days

  • Wed 16 Sept Max en route +9 min · last fix heading to Niederbipp +6 min

Distribution · 90 days

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

  • Early 19% · 6
  • On time 78% · 25
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=2
  • 100% T n=6
  • 83% W n=6
  • 100% T n=2
  • 100% F n=5
  • 100% S n=5
  • 100% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (15 stops).

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