S11 426 Oensingen – Langenthal

View line S11

Oensingen 16:44 → Langenthal 17:06 Daily 0 h 22 min · 13 stops Aare Seeland mobil

✓ Today’s run finished

Today it reached Langenthal at 17:06 0 min

  1. Oensingen16:44
  2. Niederbipp16:46
  3. Scharnageln16:48
  4. Bannwil16:52
  5. Aarwangen16:58
  6. Hard-Mumenthal17:00
  7. Langenthal17:06

Next service: tomorrow 16:44 from Oensingen · Fri 6 Nov

Next departure 16:44 tomorrow · Oensingen
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
98%
39/40 runs under 3 min
RT coverage: 40 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 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

Worst days

  • Thu 3 Sept Max en route +10 min · last fix heading to Les Planches (Aigle) +10 min

Distribution · 90 days

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

  • Early 13% · 5
  • On time 85% · 34
  • 3–10 min 0% · 0
  • 10–30 min 3% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (13 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
16:44on time on time
16:45≈ on time ≈ on time
16:46≈ on time ≈ on time
16:47≈ on time ≈ on time
16:48≈ on time ≈ on time
16:49≈ on time ≈ on time
16:52≈ on time ≈ +1 min
16:55≈ on time ≈ +1 min
16:58≈ on time ≈ +1 min
16:59≈ on time ≈ +1 min
17:00≈ on time ≈ +1 min
17:01≈ on time ≈ +1 min
17:06on 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
Thu 5 NovLangenthal 10:340 min+2 min
Wed 4 NovLangenthal 10:34+1 min+1 min
Tue 3 NovLangenthal 10:34+1 min+2 min
Mon 2 NovLangenthal 10:340 min+2 min
Sun 1 NovApples 12:110 min+2 min
Sat 31 OctApples 12:110 min+1 min
Fri 30 OctLangenthal 10:350 min+2 min
Thu 29 OctLangenthal 10:37No data—
Wed 28 OctLangenthal 10:35−1 min+2 min
Tue 27 OctLangenthal 10:360 min+3 min
Mon 26 OctOensingen 11:01−2 min+1 min
Sun 25 OctApples 12:11+1 min+3 min
Sat 24 OctApples 12:12+1 min+1 min
Fri 23 OctLangenthal 10:340 min—
Thu 22 OctLangenthal 10:39+3 min+5 min
Wed 21 OctLangenthal 10:350 min+1 min
Tue 20 OctLangenthal 10:35−1 min+2 min
Mon 19 OctLangenthal 10:350 min+2 min
Sun 18 OctApples 12:120 min+2 min
Sat 17 OctApples 12:110 min+1 min
Fri 16 OctLangenthal 10:36−1 min+3 min
Thu 15 OctLangenthal 10:36−1 min+2 min
Wed 14 OctLangenthal 10:36−1 min+3 min
Tue 13 OctLangenthal 10:350 min+1 min
Mon 12 OctLangenthal 10:36−1 min+2 min
Sun 11 OctApples 12:13+2 min+2 min
Sat 10 OctApples 12:120 min+2 min
Fri 9 OctLangenthal 10:350 min+1 min
Thu 8 OctLangenthal 10:35−1 min+1 min
Wed 7 OctLangenthal 10:35−1 min—