S23 8466 Olten – Langenthal

View line S23

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

It has not run yet today

Last recorded run: Tuesday 10 November 0 min

Next service: today 18:16 from Olten · Wed 11 Nov

Next departure 18:16 today · Olten
On-time · 30 days
100%
28/28 runs under 3 min
RT coverage: 28 full · 0 partial · 1 no data
On-time · 90 days
100%
41/41 runs under 3 min
RT coverage: 41 full · 0 partial · 1 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

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

  • Early 12% · 5
  • On time 88% · 36
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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