S11 9453 Oensingen – Solothurn

View line S11

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

✓ Today’s run finished

Today it reached Solothurn at 17:42 −1 min

  1. Oensingen17:17
  2. Niederbipp17:19
  3. Wiedlisbach17:24
  4. Flumenthal17:29
  5. Bei den Weihern17:32
  6. Solothurn Sternen17:37
  7. Solothurn17:42

Next service: tomorrow 17:17 from Oensingen · Mon 9 Nov

Next departure 17: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
95%
40/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 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

  • Fri 6 Nov Max en route +3 min · last fix heading to Solothurn +3 min
  • Mon 5 Oct Max en route +3 min · last fix heading to Solothurn +3 min

Distribution · 90 days

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

  • Early 12% · 5
  • On time 83% · 35
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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
17:17on time +1 min
17:18≈ on time ≈ +1 min
17:19≈ on time ≈ +1 min
17:20≈ on time ≈ +1 min
17:22≈ on time ≈ +1 min
17:24≈ on time ≈ +1 min
17:27≈ on time ≈ +1 min
17:29≈ on time ≈ +1 min
17:31≈ on time ≈ +2 min
17:32≈ on time ≈ +2 min
17:35≈ on time ≈ +2 min
17:36≈ on time ≈ +2 min
17:37≈ on time ≈ +2 min
17:38≈ on time ≈ +2 min
17: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
Sun 8 NovSolothurn 17:42−1 min—
Sat 7 NovSolothurn 17:430 min+1 min
Fri 6 NovSolothurn 17:44+3 min+3 min
Thu 5 NovSolothurn 17:44+1 min—
Wed 4 NovSolothurn 17:44+3 min+3 min
Tue 3 NovSolothurn 17:440 min—
Mon 2 NovSolothurn 17:44+1 min+1 min
Sun 1 NovSolothurn 17:41−1 min—
Sat 31 OctSolothurn 17:44+1 min+1 min
Fri 30 OctSolothurn 17:420 min—
Thu 29 OctSolothurn 17:44+1 min+1 min
Wed 28 OctSolothurn 17:440 min—
Tue 27 OctSolothurn 17:42−2 min—
Mon 26 OctSolothurn 17:45+2 min+2 min
Sun 25 OctSolothurn 17:41−2 min—
Sat 24 OctSolothurn 17:44+1 min+1 min
Fri 23 OctSolothurn 17:44+1 min+1 min
Thu 22 OctSolothurn 17:45+1 min+2 min
Wed 21 OctSolothurn 17:45+2 min+3 min
Tue 20 OctSolothurn 17:430 min+1 min
Mon 19 OctSolothurn 17:420 min—
Sun 18 OctSolothurn 17:41−1 min—
Sat 17 OctSolothurn 17:45+2 min+2 min
Fri 16 OctSolothurn 17:45+2 min+2 min
Thu 15 OctSolothurn 17:430 min+1 min
Wed 14 OctSolothurn 17:430 min+2 min
Tue 13 OctSolothurn 17:46+2 min+3 min
Mon 12 OctSolothurn 17:42+1 min—
Sun 11 OctSolothurn 17:41−1 min—
Sat 10 OctSolothurn 17:42−2 min—