S23 8482 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: Sunday 8 November −1 min

Next service: tomorrow 18:16 from Olten · Tue 10 Nov

Next departure 18:16 tomorrow · Olten
On-time · 30 days
96%
26/27 runs under 3 min
RT coverage: 27 full · 0 partial · 1 no data
On-time · 90 days
94%
34/36 runs under 3 min
RT coverage: 36 full · 0 partial · 1 no data
Typical delay
−1min
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

  • Fri 23 Oct Max en route +4 min · last fix heading to Langenthal +4 min
  • Sat 3 Oct Max en route +4 min · last fix heading to Langenthal +4 min

Distribution · 90 days

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

  • Early 14% · 5
  • On time 81% · 29
  • 3–10 min 6% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=5
  • 100% T n=6
  • 100% W n=3
  • 100% T n=5
  • 80% F n=5
  • 83% S n=6
  • 100% S n=6

Stops and timetable

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

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