S20 7718 Oensingen – Langendorf

View line S20

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

✓ Today’s run finished

Today, last fix heading to Langendorf at 11:52 No data

  1. Oensingen11:28
  2. Niederbipp11:30
  3. Wangen an der Aare11:35
  4. Luterbach-Attisholz11:41
  5. Solothurn11:45
  6. Solothurn West11:47
  7. Langendorf11:51

Next service: tomorrow 11:28 from Oensingen · Fri 6 Nov

Next departure 11:28 tomorrow · Oensingen
On-time · 30 days
100%
22/22 runs under 3 min
RT coverage: 22 full · 0 partial · 8 no data
On-time · 90 days
100%
58/58 runs under 3 min
RT coverage: 58 full · 0 partial · 15 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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 58
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=9
  • 100% W n=10
  • 100% T n=5
  • 100% F n=9
  • 100% S n=12
  • 100% S n=8

Stops and timetable

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

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