S11 466 Oensingen – Langenthal

View line S11

Oensingen 20:14 → Langenthal 20:36 Daily 0 h 22 min · 13 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Langenthal at 20:36 −2 min

  1. Oensingen20:14
  2. Niederbipp20:16
  3. Scharnageln20:18
  4. Bannwil20:22
  5. Aarwangen20:28
  6. Hard-Mumenthal20:30
  7. Langenthal20:36

Next service: tomorrow 20:14 from Oensingen · Tue 10 Nov

Full trip card
Next departure 20:14 tomorrow · Oensingen
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%
44/44 runs under 3 min
RT coverage: 44 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Langenthal, 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

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

  • Early 64% · 28
  • On time 36% · 16
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=6
  • 100% T n=7
  • 100% W n=8
  • 100% T n=7
  • 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 (13 stops).

Last 90 days, 44 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
Oensingen
20:14on time on time
Niederbipp Industrie
20:15≈ on time ≈ on time
Niederbipp
20:16≈ on time ≈ on time
Niederbipp Dorf
20:17≈ on time ≈ on time
Scharnageln
20:18≈ on time ≈ on time
Holzhäusern
20:19≈ on time ≈ on time
Bannwil
20:22≈ on time ≈ on time
Aarwangen Schloss
20:25≈ 1 min early ≈ on time
Aarwangen
20:28≈ 1 min early ≈ on time
Aarwangen Vorstadt
20:29≈ 1 min early ≈ on time
Hard-Mumenthal
20:30≈ 1 min early ≈ on time
Langenthal Gaswerk
20:31≈ 1 min early ≈ +1 min
Langenthal
20:362 min early +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
Mon 9 NovLangenthal 20:34−2 min+2 min
Sun 8 NovLangenthal 20:340 min+1 min
Sat 7 NovLangenthal 20:34+1 min+2 min
Fri 6 NovLangenthal 20:33+1 min+2 min
Thu 5 NovLangenthal 20:34−3 min—
Wed 4 NovLangenthal 20:34−1 min—
Tue 3 NovLangenthal 20:34−1 min+1 min
Mon 2 NovLangenthal 20:34−1 min—
Sun 1 NovLangenthal 20:34+1 min+1 min
Sat 31 OctLangenthal 20:35−2 min+2 min
Fri 30 OctLangenthal 20:35−1 min+2 min
Thu 29 OctLangenthal 20:34−1 min—
Wed 28 OctLangenthal 20:35−2 min+1 min
Tue 27 OctLangenthal 20:360 min+3 min
Mon 26 OctLangenthal 20:35−2 min—
Sun 25 OctLangenthal 20:34−2 min—
Sat 24 OctLangenthal 20:35−2 min+3 min
Fri 23 OctLangenthal 20:35−2 min+2 min
Thu 22 OctLangenthal 20:35−2 min+1 min
Wed 21 OctLangenthal 20:35−1 min+2 min
Tue 20 OctLangenthal 20:35−2 min+3 min
Mon 19 OctLangenthal 20:34−3 min—
Sun 18 OctLangenthal 20:370 min+3 min
Sat 17 OctLangenthal 20:35−2 min+1 min
Fri 16 OctLangenthal 20:35−1 min+2 min
Thu 15 OctLangenthal 20:36−1 min+2 min
Wed 14 OctLangenthal 20:37−1 min+2 min
Tue 13 OctLangenthal 20:36−1 min+2 min
Mon 12 OctLangenthal 20:36−1 min+2 min
Sun 11 OctLangenthal 20:35−2 min+2 min