S23 8426 Olten – Langenthal

View line S23

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

✓ Today’s run finished

Today it reached Langenthal at 08:36 0 min

  1. Olten08:16
  2. Aarburg-Oftringen08:19
  3. Rothrist08:23
  4. Murgenthal08:28
  5. Roggwil-Wynau08:30
  6. Langenthal08:36

Next service: tomorrow 08:16 from Olten · Sat 14 Nov

Next departure 08:16 tomorrow · Olten
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
43/43 runs under 3 min
RT coverage: 43 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 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

Distribution · 90 days

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

  • Early 9% · 4
  • On time 91% · 39
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 43 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
08:16on time on time
08:19 / 08:20≈ on time ≈ on time
08:23 / 08:24≈ on time ≈ on time
08:28≈ on time ≈ on time
08:30≈ on time ≈ on time
08:36on time on time

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
Fri 13 NovLangenthal 08:370 min—
Thu 12 NovLangenthal 08:370 min—
Wed 11 NovLangenthal 08:340 min—
Tue 10 NovLangenthal 08:340 min—
Mon 9 NovLangenthal 08:38+1 min—
Sun 8 NovLangenthal 08:34−1 min—
Sat 7 NovLangenthal 08:340 min—
Fri 6 NovLangenthal 08:370 min—
Thu 5 NovLangenthal 08:340 min—
Wed 4 NovLangenthal 08:340 min—
Tue 3 NovLangenthal 08:340 min—
Mon 2 NovLangenthal 08:340 min—
Sun 1 NovLangenthal 08:36−1 min—
Sat 31 OctLangenthal 08:36−1 min—
Fri 30 OctLangenthal 08:370 min—
Thu 29 OctLangenthal 08:36−1 min—
Wed 28 OctLangenthal 08:370 min—
Tue 27 OctLangenthal 08:37−1 min—
Mon 26 OctLangenthal 08:370 min—
Sun 25 OctLangenthal 08:38+1 min—
Sat 24 OctLangenthal 08:39+1 min+1 min
Fri 23 OctLangenthal 08:36−1 min—
Thu 22 OctLangenthal 08:370 min—
Wed 21 OctLangenthal 08:380 min—
Tue 20 OctLangenthal 08:370 min—
Mon 19 OctLangenthal 08:370 min—
Sun 18 OctLangenthal 08:36−1 min—
Sat 17 OctLangenthal 08:36−1 min—
Fri 16 OctLangenthal 08:36−1 min—
Thu 15 OctLangenthal 08:370 min—