S11 414 Oensingen – Langenthal

View line S11

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

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 16:14 from Oensingen · Fri 13 Nov

Next departure 16:14 today · Oensingen
On-time · 30 days
93%
27/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
93%
43/46 runs under 3 min
RT coverage: 46 full · 0 partial · 0 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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

  • Mon 12 Oct Max en route +12 min · last fix heading to Langenthal +9 min
  • Wed 11 Nov Max en route +4 min · last fix heading to Langenthal +4 min
  • Wed 4 Nov Max en route +3 min · last fix heading to Langenthal +3 min

Distribution · 90 days

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

  • Early 4% · 2
  • On time 89% · 41
  • 3–10 min 7% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 86% M n=7
  • 100% T n=6
  • 75% W n=8
  • 100% T n=8
  • 100% F n=6
  • 100% S n=5
  • 100% S n=6

Stops and timetable

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

Last 90 days, 46 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:14on time on time
16:15≈ on time ≈ on time
16:16≈ on time ≈ on time
16:17≈ on time ≈ on time
16:18≈ on time ≈ +1 min
16:19≈ on time ≈ +1 min
16:22≈ on time ≈ +1 min
16:25≈ on time ≈ +1 min
16:28≈ on time ≈ +2 min
16:29≈ on time ≈ +2 min
16:30≈ on time ≈ +2 min
16:31≈ on time ≈ +2 min
16:36+1 min +3 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 12 NovLangenthal 07:370 min+2 min
Wed 11 NovLangenthal 07:39+4 min+4 min
Tue 10 NovLangenthal 07:34+1 min+2 min
Mon 9 NovLangenthal 07:39+3 min+4 min
Sun 8 NovApples 09:120 min+2 min
Sat 7 NovApples 09:12+1 min+2 min
Fri 6 NovLangenthal 07:370 min+2 min
Thu 5 NovLangenthal 07:370 min+2 min
Wed 4 NovLangenthal 07:39+3 min+3 min
Tue 3 NovLangenthal 07:38+1 min+2 min
Mon 2 NovLangenthal 07:38+1 min+3 min
Sun 1 NovApples 09:110 min+2 min
Sat 31 OctApples 09:12+1 min+2 min
Fri 30 OctLangenthal 07:370 min—
Thu 29 OctLangenthal 07:36+1 min+3 min
Wed 28 OctLangenthal 07:38+1 min+3 min
Tue 27 OctLangenthal 07:380 min+3 min
Mon 26 OctLangenthal 07:370 min+3 min
Sun 25 OctApples 09:110 min+2 min
Sat 24 OctApples 09:14+3 min+3 min
Fri 23 OctLangenthal 07:38+1 min+4 min
Thu 22 OctLangenthal 07:38+1 min+3 min
Wed 21 OctLangenthal 07:40+3 min+4 min
Tue 20 OctLangenthal 07:39+1 min+3 min
Mon 19 OctLangenthal 07:35−1 min+2 min
Sun 18 OctApples 09:12+1 min+2 min
Sat 17 OctApples 09:12+1 min+2 min
Fri 16 OctLangenthal 07:360 min+2 min
Thu 15 OctLangenthal 07:380 min+3 min
Wed 14 OctLangenthal 07:36+1 min+2 min