S23 8438 Olten – Langenthal

View line S23

Olten 11:16 → Langenthal 11:36 Daily 0 h 20 min · 6 stops SBB CFF FFS

✓ Today’s run finished

Today it reached Langenthal at 11:36 0 min

  1. Olten11:16
  2. Aarburg-Oftringen11:19
  3. Rothrist11:23
  4. Murgenthal11:28
  5. Roggwil-Wynau11:30
  6. Langenthal11:36

Next service: tomorrow 11:16 from Olten · Thu 12 Nov

Next departure 11:16 tomorrow · Olten
On-time · 30 days
90%
19/21 runs under 3 min
RT coverage: 21 full · 0 partial · 9 no data
On-time · 90 days
94%
29/31 runs under 3 min
RT coverage: 31 full · 0 partial · 11 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
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 +31 min · last fix heading to Murgenthal +31 min
  • Sun 25 Oct Max en route +5 min · last fix heading to Langenthal +5 min

Distribution · 90 days

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

  • Early 16% · 5
  • On time 77% · 24
  • 3–10 min 3% · 1
  • 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=1
  • 100% F n=4
  • 100% S n=5
  • 67% S n=6

Stops and timetable

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

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