S11 433 Langenthal → Oensingen

View line S11

Langenthal 11:52 → Oensingen 12:13 Daily 0 h 21 min · 13 stops Aare Seeland mobil

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

✓ Today’s run finished

Today it reached Oensingen at 12:13 −1 min

  1. Langenthal11:52
  2. Hard-Mumenthal11:55
  3. Aarwangen11:58
  4. Bannwil12:02
  5. Scharnageln12:06
  6. Niederbipp12:09
  7. Oensingen12:13

Next service: tomorrow 11:52 from Langenthal · Sun 22 Nov

Next departure 11:52 tomorrow · Langenthal
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%
37/37 runs under 3 min
RT coverage: 37 full · 0 partial · 12 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: +2 min

Last 30 days

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

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

  • Early 14% · 5
  • On time 86% · 32
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=1
  • 100% T n=7
  • 100% W n=7
  • 100% T n=1
  • 100% 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, 37 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:52on time on time
11:53≈ on time ≈ on time
11:55≈ on time ≈ on time
11:56≈ on time ≈ on time
11:58≈ on time ≈ +1 min
11:59≈ on time ≈ +1 min
12:02≈ on time ≈ +1 min
12:05≈ on time ≈ +1 min
12:06≈ on time ≈ +1 min
12:07≈ on time ≈ +1 min
12:09≈ on time ≈ +1 min
12:10≈ on time ≈ +2 min
12:13on 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 NovOensingen 12:13−1 min—
Fri 20 NovOensingen 12:130 min—
Thu 19 NovOensingen 12:14No data—
Wed 18 NovOensingen 12:14+3 min+3 min
Tue 17 NovOensingen 12:14−1 min+1 min
Mon 16 NovOensingen 12:14No data—
Sun 15 NovOensingen 12:140 min+1 min
Sat 14 NovOensingen 12:13+1 min—
Fri 13 NovOensingen 12:13−1 min—
Thu 12 NovOensingen 12:14No data—
Wed 11 NovOensingen 12:140 min—
Tue 10 NovOensingen 12:120 min—
Mon 9 NovOensingen 12:14No data—
Sun 8 NovOensingen 12:130 min+1 min
Sat 7 NovOensingen 12:13−1 min—
Fri 6 NovOensingen 12:140 min—
Thu 5 NovOensingen 12:14No data—
Wed 4 NovOensingen 12:14+2 min+2 min
Tue 3 NovOensingen 12:14−1 min—
Mon 2 NovOensingen 12:14No data—
Sun 1 NovOensingen 12:15+2 min+2 min
Sat 31 OctOensingen 12:15+1 min—
Fri 30 OctOensingen 12:15+1 min+1 min
Thu 29 OctOensingen 12:14No data—
Wed 28 OctOensingen 12:15+1 min—
Tue 27 OctOensingen 12:150 min—
Mon 26 OctOensingen 12:15No data—
Sun 25 OctOensingen 12:130 min—
Sat 24 OctOensingen 12:15+1 min+2 min
Fri 23 OctOensingen 12:130 min—