S23 8462 Olten – Langenthal

View line S23

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

✓ Today’s run finished

Today it reached Langenthal at 17:37 +1 min

  1. Olten17:16
  2. Aarburg-Oftringen17:19
  3. Rothrist17:23
  4. Murgenthal17:28
  5. Roggwil-Wynau17:30
  6. Langenthal17:36

Next service: tomorrow 17:16 from Olten · Tue 17 Nov

Next departure 17: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 · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 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

Distribution · 90 days

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

  • Early 19% · 8
  • On time 81% · 35
  • 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=6
  • 100% F n=6
  • 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, 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
17:16on time on time
17:19 / 17:20≈ on time ≈ on time
17:23 / 17:24≈ on time ≈ +1 min
17:28≈ on time ≈ +1 min
17:30≈ on time ≈ +1 min
17: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
Mon 16 NovLangenthal 17:37+1 min—
Sun 15 NovLangenthal 17:34−1 min—
Sat 14 NovLangenthal 17:340 min—
Fri 13 NovLangenthal 17:34−1 min—
Thu 12 NovLangenthal 17:39+2 min+2 min
Wed 11 NovLangenthal 17:38+1 min+1 min
Tue 10 NovLangenthal 17:37+1 min+4 min
Mon 9 NovLangenthal 17:39+2 min+2 min
Sun 8 NovLangenthal 17:370 min—
Sat 7 NovLangenthal 17:370 min—
Fri 6 NovLangenthal 17:38+2 min+2 min
Thu 5 NovLangenthal 17:340 min—
Wed 4 NovLangenthal 17:38+1 min—
Tue 3 NovLangenthal 17:370 min—
Mon 2 NovLangenthal 17:38+1 min—
Sun 1 NovLangenthal 17:370 min—
Sat 31 OctLangenthal 17:370 min—
Fri 30 OctLangenthal 17:36−1 min—
Thu 29 OctLangenthal 17:38+1 min—
Wed 28 OctLangenthal 17:370 min—
Tue 27 OctLangenthal 17:38+1 min—
Mon 26 OctLangenthal 17:36−1 min—
Sun 25 OctLangenthal 17:39+1 min+1 min
Sat 24 OctLangenthal 17:39+1 min—
Fri 23 OctLangenthal 17:36−1 min—
Thu 22 OctLangenthal 17:38+1 min+1 min
Wed 21 OctLangenthal 17:36−1 min—
Tue 20 OctLangenthal 17:36−1 min—
Mon 19 OctLangenthal 17:360 min—
Sun 18 OctLangenthal 17:36−1 min—