S11 445 Langenthal – Oensingen

View line S11

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

✓ Today’s run finished

Today it reached Oensingen at 15:14 +1 min

  1. Langenthal14:52
  2. Hard-Mumenthal14:55
  3. Aarwangen14:58
  4. Bannwil15:02
  5. Scharnageln15:06
  6. Niederbipp15:09
  7. Oensingen15:13

Next service: tomorrow 14:52 from Langenthal · Wed 18 Nov

Next departure 14:52 tomorrow · Langenthal
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
44/45 runs under 3 min
RT coverage: 45 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 Oensingen, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Sat 10 Oct Max en route +3 min · last fix heading to Oensingen +3 min

Distribution · 90 days

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

  • Early 11% · 5
  • On time 87% · 39
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 45 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
14:52on time on time
14:53≈ on time ≈ on time
14:55≈ on time ≈ on time
14:56≈ on time ≈ on time
14:58≈ on time ≈ on time
14:59≈ on time ≈ +1 min
15:02≈ on time ≈ +1 min
15:05≈ on time ≈ +1 min
15:06≈ on time ≈ +1 min
15:07≈ on time ≈ +1 min
15:09≈ on time ≈ +1 min
15:10≈ on time ≈ +1 min
15: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
Tue 17 NovOensingen 15:14+1 min—
Mon 16 NovOensingen 15:130 min+2 min
Sun 15 NovOensingen 15:130 min—
Sat 14 NovOensingen 15:12+1 min—
Fri 13 NovOensingen 15:14+1 min+1 min
Thu 12 NovOensingen 15:120 min—
Wed 11 NovOensingen 15:140 min—
Tue 10 NovOensingen 15:130 min—
Mon 9 NovOensingen 15:14+1 min+2 min
Sun 8 NovOensingen 15:13−1 min—
Sat 7 NovOensingen 15:140 min+2 min
Fri 6 NovOensingen 15:140 min—
Thu 5 NovOensingen 15:13+1 min—
Wed 4 NovOensingen 15:140 min—
Tue 3 NovOensingen 15:14+3 min+3 min
Mon 2 NovOensingen 15:140 min—
Sun 1 NovOensingen 15:140 min+1 min
Sat 31 OctOensingen 15:13+1 min+1 min
Fri 30 OctOensingen 15:12+1 min—
Thu 29 OctOensingen 15:15+1 min+2 min
Wed 28 OctOensingen 15:16+2 min+2 min
Tue 27 OctOensingen 15:150 min—
Mon 26 OctOensingen 15:13−1 min—
Sun 25 OctOensingen 15:12−1 min—
Sat 24 OctOensingen 15:13−1 min—
Fri 23 OctOensingen 15:15+1 min+2 min
Thu 22 OctOensingen 15:15+1 min—
Wed 21 OctOensingen 15:15+1 min+1 min
Tue 20 OctOensingen 15:150 min—
Mon 19 OctOensingen 15:140 min—