S11 448 Oensingen → Langenthal

View line S11

Oensingen 15:44 → Langenthal 16:06 Mon, Tue, Wed, Thu, Fri, Sat 0 h 22 min · 13 stops Aare Seeland mobil

S11 448 Oensingen–Langenthal: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 19:12 (GMT+1).

✓ Today’s run finished

Today it reached Langenthal at 16:06 −1 min

  1. Oensingen15:44
  2. Niederbipp15:46
  3. Scharnageln15:48
  4. Bannwil15:52
  5. Aarwangen15:58
  6. Hard-Mumenthal16:00
  7. Langenthal16:06

Next service: Monday 15:44 from Oensingen · Mon 23 Nov

Next departure 15:44 Monday · 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
96%
47/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 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

  • Sun 18 Oct Max en route +7 min · last fix heading to Les Diablerets +6 min
  • Sun 4 Oct Max en route +7 min · last fix heading to Les Diablerets +6 min

Distribution · 90 days

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

  • Early 6% · 3
  • On time 90% · 44
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=7
  • 100% F n=7
  • 100% S n=7
  • 71% S n=7

Stops and timetable

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

Last 90 days, 49 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
15:44+1 min +3 min
15:45≈ +1 min ≈ +3 min
15:46≈ +1 min ≈ +3 min
15:47≈ +1 min ≈ +3 min
15:48≈ +1 min ≈ +3 min
15:49≈ +1 min ≈ +2 min
15:52≈ +1 min ≈ +2 min
15:55≈ +1 min ≈ +2 min
15:58≈ +1 min ≈ +2 min
15:59≈ +1 min ≈ +2 min
16:00≈ +1 min ≈ +2 min
16:01≈ +1 min ≈ +2 min
16: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
Sat 21 NovLangenthal 16:04−1 min+1 min
Fri 20 NovLangenthal 16:04+1 min+2 min
Thu 19 NovLangenthal 16:04+1 min+4 min
Wed 18 NovLangenthal 16:040 min+3 min
Tue 17 NovLangenthal 16:08+1 min+4 min
Mon 16 NovLangenthal 16:04+1 min+2 min
Sun 15 NovLes Diablerets 15:190 min+1 min
Sat 14 NovLangenthal 16:040 min+5 min
Fri 13 NovLangenthal 16:040 min+5 min
Thu 12 NovLangenthal 16:040 min+2 min
Wed 11 NovLangenthal 16:040 min+2 min
Tue 10 NovLangenthal 16:04+1 min+2 min
Mon 9 NovLangenthal 16:070 min+2 min
Sun 8 NovLes Diablerets 15:190 min—
Sat 7 NovLangenthal 16:040 min+1 min
Fri 6 NovLangenthal 16:07+2 min+2 min
Thu 5 NovLangenthal 16:070 min+1 min
Wed 4 NovLangenthal 16:07+1 min+2 min
Tue 3 NovLangenthal 16:07+1 min+2 min
Mon 2 NovLangenthal 16:07+1 min+3 min
Sun 1 NovLes Diablerets 15:200 min+2 min
Sat 31 OctLangenthal 16:050 min+2 min
Fri 30 OctLangenthal 16:070 min+5 min
Thu 29 OctLangenthal 16:10+3 min+5 min
Wed 28 OctLangenthal 16:06−1 min+2 min
Tue 27 OctLangenthal 16:06+1 min+5 min
Mon 26 OctLangenthal 16:09+2 min+3 min
Sun 25 OctLes Diablerets 15:18−1 min+2 min
Sat 24 OctLangenthal 16:05−2 min+4 min
Fri 23 OctLangenthal 16:06−1 min+5 min