S20 7713 Langendorf – Oensingen

View line S20

Langendorf 08:09 → Oensingen 08:32 Daily 0 h 23 min · 8 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Oensingen at 08:32 −1 min

  1. Langendorf08:09
  2. Solothurn West08:11
  3. Solothurn08:14
  4. Deitingen08:21
  5. Wangen an der Aare08:24
  6. Niederbipp08:29
  7. Oensingen08:32

Next service: tomorrow 08:09 from Langendorf · Sun 8 Nov

Full trip card
Next departure 08:09 tomorrow · Langendorf
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
40/40 runs under 3 min
RT coverage: 40 full · 0 partial · 0 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

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

  • Early 3% · 1
  • On time 98% · 39
  • 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=5
  • 100% W n=5
  • 100% T n=5
  • 100% F n=5
  • 100% S n=7
  • 100% S n=6

Stops and timetable

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

Last 90 days, 40 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
Langendorf
08:09on time on time
Solothurn West
08:11≈ on time ≈ on time
Solothurn
08:14 / 08:16≈ on time ≈ on time
Luterbach-Attisholz
08:18 / 08:19≈ on time ≈ on time
Deitingen
08:21 / 08:22≈ on time ≈ on time
Wangen an der Aare
08:24≈ on time ≈ on time
Niederbipp
08:29≈ on time ≈ +1 min
Oensingen
08:32on 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 7 NovOensingen 08:32−1 min—
Fri 6 NovOensingen 08:34+1 min—
Thu 5 NovOensingen 08:330 min—
Wed 4 NovOensingen 08:33+1 min—
Tue 3 NovOensingen 08:330 min—
Mon 2 NovOlten 08:520 min—
Sun 1 NovOlten 08:500 min—
Sat 31 OctOlten 08:510 min—
Fri 30 OctOlten 08:52+1 min—
Thu 29 OctOlten 08:510 min—
Wed 28 OctOlten 08:520 min—
Tue 27 OctOlten 08:520 min—
Mon 26 OctOlten 08:510 min—
Sun 25 OctOlten 08:51+1 min—
Sat 24 OctOlten 08:52+1 min+2 min
Fri 23 OctOlten 08:510 min—
Thu 22 OctOlten 08:510 min—
Wed 21 OctOlten 08:520 min—
Tue 20 OctOlten 08:510 min—
Mon 19 OctOlten 08:510 min—
Sun 18 OctOlten 08:50−1 min—
Sat 17 OctOlten 08:52+1 min—
Fri 16 OctOlten 08:510 min—
Thu 15 OctOlten 08:510 min—
Wed 14 OctOlten 08:510 min—
Tue 13 OctOlten 08:51−1 min—
Mon 12 OctOlten 08:50−1 min—
Sun 11 OctOlten 08:52+1 min—
Sat 10 OctOlten 08:52+1 min—
Fri 9 OctOlten 08:50−1 min—