S23 8478 Olten – Langenthal

View line S23

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

✓ Today’s run finished

Today it reached Langenthal at 21:38 +2 min

  1. Olten21:16
  2. Aarburg-Oftringen21:19
  3. Rothrist21:23
  4. Murgenthal21:28
  5. Roggwil-Wynau21:30
  6. Langenthal21:36

Next service: tomorrow 21:16 from Olten · Fri 13 Nov

Next departure 21:16 tomorrow · Olten
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
39/41 runs under 3 min
RT coverage: 41 full · 0 partial · 0 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
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

  • Fri 23 Oct Max en route +6 min · last fix heading to Langenthal +6 min
  • Mon 26 Oct Max en route +3 min · last fix heading to Langenthal +3 min

Distribution · 90 days

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

  • Early 20% · 8
  • On time 76% · 31
  • 3–10 min 5% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

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