S20 7716 Oensingen – Langendorf

View line S20

Oensingen 10:28 → Langendorf 10:51 Daily 0 h 23 min · 8 stops SBB CFF FFS

It has not run yet today

Last recorded run: Saturday 7 November 0 min

Next service: today 10:28 from Oensingen · Sun 8 Nov

Next departure 10:28 today · Oensingen
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 2 no data
On-time · 90 days
99%
69/70 runs under 3 min
RT coverage: 70 full · 0 partial · 2 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 Langendorf, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 7 Sept Max en route +3 min · last fix heading to Solothurn +3 min

Distribution · 90 days

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

  • Early 4% · 3
  • On time 94% · 66
  • 3–10 min 1% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 90% M n=10
  • 100% T n=10
  • 100% W n=11
  • 100% T n=10
  • 100% F n=10
  • 100% S n=12
  • 100% S n=7

Stops and timetable

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

Last 90 days, 71 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
10:28+1 min +1 min
10:30≈ +1 min ≈ +1 min
10:35 / 10:36≈ on time ≈ +1 min
10:38≈ on time ≈ +1 min
10:41≈ on time ≈ +1 min
10:45 / 10:46≈ on time ≈ +1 min
10:47 / 10:48≈ on time ≈ +1 min
10:51on 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 NovLangendorf 10:520 min—
Fri 6 NovSolothurn 10:470 min—
Thu 5 NovSolothurn 10:44+1 min—
Wed 4 NovSolothurn 10:44+1 min—
Tue 3 NovSolothurn 10:44+1 min—
Mon 2 NovSolothurn 10:44+1 min—
Sun 1 NovSolothurn 10:460 min—
Sat 31 OctLangendorf 10:51−1 min—
Fri 30 OctSolothurn 10:45−1 min—
Thu 29 OctSolothurn 10:46No data—
Wed 28 OctSolothurn 10:470 min—
Tue 27 OctSolothurn 10:47+1 min—
Mon 26 OctOlten 11:010 min—
Sun 25 OctSolothurn 10:46No data—
Sat 24 OctLangendorf 10:520 min—
Fri 23 OctSolothurn 10:450 min—
Thu 22 OctSolothurn 10:49+3 min+3 min
Wed 21 OctSolothurn 10:47+1 min+1 min
Tue 20 OctSolothurn 10:47+1 min—
Mon 19 OctSolothurn 10:47+1 min+1 min
Sun 18 OctSolothurn 10:470 min—
Sat 17 OctLangendorf 10:52−1 min—
Fri 16 OctSolothurn 10:47+1 min—
Thu 15 OctSolothurn 10:460 min—
Wed 14 OctSolothurn 10:460 min—
Tue 13 OctSolothurn 10:460 min—
Mon 12 OctSolothurn 10:460 min—
Sun 11 OctSolothurn 10:460 min—
Sat 10 OctLangendorf 10:53+1 min—
Fri 9 OctSolothurn 10:47+1 min—