S11 434 Oensingen → Langenthal

View line S11

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

S11 434 Oensingen–Langenthal: final delay under 3 min on 22 of its 23 runs with data in the last 30 days (96%). Median final delay: +1 min. TrainsRadar data as of 21 Nov 2026, 16:02 (GMT+1).

✓ Today’s run finished

Today it reached Langenthal at 12:36 0 min

  1. Oensingen12:14
  2. Niederbipp12:16
  3. Scharnageln12:18
  4. Bannwil12:22
  5. Aarwangen12:28
  6. Hard-Mumenthal12:30
  7. Langenthal12:36

Next service: tomorrow 12:14 from Oensingen · Sun 22 Nov

Next departure 12:14 tomorrow · Oensingen
On-time · 30 days
96%
22/23 runs under 3 min
RT coverage: 23 full · 0 partial · 7 no data
On-time · 90 days
97%
38/39 runs under 3 min
RT coverage: 39 full · 0 partial · 10 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 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

  • Fri 20 Nov Max en route +100 min · last fix heading to Zürich HB +91 min

Distribution · 90 days

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

  • Early 33% · 13
  • On time 64% · 25
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 3% · 1

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=3
  • 86% F n=7
  • 100% S n=7
  • 100% S n=7

Stops and timetable

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

Last 90 days, 39 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
12:14on time on time
12:15≈ on time ≈ on time
12:16≈ on time ≈ on time
12:17≈ on time ≈ on time
12:18≈ on time ≈ on time
12:19≈ on time ≈ on time
12:22≈ on time ≈ +1 min
12:25≈ on time ≈ +1 min
12:28≈ on time ≈ +1 min
12:29≈ on time ≈ +1 min
12:30≈ on time ≈ +1 min
12:31≈ on time ≈ +1 min
12:36on 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 12:340 min+3 min
Fri 20 NovZürich HB 12:52+91 min+100 min
Thu 19 NovLangenthal 12:370 min—
Wed 18 NovLangenthal 12:38+1 min+3 min
Tue 17 NovLangenthal 12:38+2 min+2 min
Mon 16 NovLangenthal 12:37No data—
Sun 15 NovLangenthal 12:34−1 min+1 min
Sat 14 NovLangenthal 12:34+1 min+2 min
Fri 13 NovLangenthal 12:34+1 min+2 min
Thu 12 NovLangenthal 12:37No data—
Wed 11 NovLangenthal 12:34+2 min+2 min
Tue 10 NovLangenthal 12:350 min+2 min
Mon 9 NovLangenthal 12:37No data—
Sun 8 NovLangenthal 12:34−2 min+1 min
Sat 7 NovLangenthal 12:34+1 min+1 min
Fri 6 NovLangenthal 12:38+1 min+4 min
Thu 5 NovLangenthal 12:37No data—
Wed 4 NovLangenthal 12:34+1 min+2 min
Tue 3 NovLangenthal 12:370 min+2 min
Mon 2 NovLangenthal 12:37No data—
Sun 1 NovLangenthal 12:35−2 min—
Sat 31 OctLangenthal 12:39+2 min+3 min
Fri 30 OctLangenthal 12:38+1 min+2 min
Thu 29 OctLangenthal 12:37No data—
Wed 28 OctLangenthal 12:360 min+2 min
Tue 27 OctLangenthal 12:370 min+3 min
Mon 26 OctLangenthal 12:37No data—
Sun 25 OctLangenthal 12:36−1 min+2 min
Sat 24 OctLangenthal 12:35−2 min+2 min
Fri 23 OctLangenthal 12:38+1 min+3 min