S23 8427 Langenthal → Olten

View line S23

Langenthal 07:21 → Olten 07:40 Daily 0 h 19 min · 6 stops SBB CFF FFS

S23 8427 Langenthal–Olten: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Olten: 07:40. TrainsRadar data as of 22 Nov 2026, 07:39 (GMT+1).

Running now · updated 07:39

Position estimated from the timetable

Between Aarburg-Oftringen and Olten −1 min

Estimated arrival at Olten 07:40 · 101 km/h

  1. Langenthal07:21
  2. Roggwil-Wynau07:25
  3. Murgenthal07:27
  4. Rothrist07:32
  5. Aarburg-Oftringen07:36
  6. Olten07:40

Today it is running no worse than usual: typical arrival delay is 0 min; 100% of the last 30 runs arrived on time.

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
98%
52/53 runs under 3 min
RT coverage: 52 full · 1 partial · 2 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 Olten, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Thu 8 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 98% · 52
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 100% T n=8
  • 100% W n=7
  • 86% T n=7
  • 100% F n=7
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 53 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 10Today
07:21on time on timePassed
07:25≈ on time ≈ on timePassed
07:27≈ on time ≈ on timePassed
07:32≈ on time ≈ +1 minPassed
07:36≈ on time ≈ +1 minPassed
07:40on time +1 minNext

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 22 NovAarburg-Oftringen 07:34Partial coverage0 min—
Sat 21 NovOlten 07:390 min—
Fri 20 NovOlten 07:39−1 min—
Thu 19 NovOlten 07:420 min—
Wed 18 NovOlten 07:42+1 min—
Tue 17 NovOlten 07:39−1 min—
Mon 16 NovOlten 07:390 min—
Sun 15 NovOlten 07:390 min—
Sat 14 NovOlten 07:39−1 min—
Fri 13 NovOlten 07:39−1 min—
Thu 12 NovOlten 07:39−1 min—
Wed 11 NovOlten 07:39−1 min—
Tue 10 NovOlten 07:42+1 min+1 min
Mon 9 NovOlten 07:390 min—
Sun 8 NovOlten 07:40−1 min—
Sat 7 NovOlten 07:390 min—
Fri 6 NovOlten 07:39−1 min—
Thu 5 NovOlten 07:42+1 min—
Wed 4 NovOlten 07:390 min—
Tue 3 NovOlten 07:420 min—
Mon 2 NovOlten 07:39−1 min—
Sun 1 NovOlten 07:410 min—
Sat 31 OctOlten 07:410 min—
Fri 30 OctOlten 07:410 min—
Thu 29 OctOlten 07:410 min—
Wed 28 OctOlten 07:410 min—
Tue 27 OctOlten 07:42+1 min—
Mon 26 OctOlten 07:42+1 min—
Sun 25 OctOlten 07:400 min—
Sat 24 OctOlten 07:410 min—