S23 8479 Langenthal – Olten

View line S23

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

It has not run yet today

Last recorded run: Wednesday 11 November 0 min

Next service: today 19:21 from Langenthal · Thu 12 Nov

Next departure 19:21 today · Langenthal
On-time · 30 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 0 no data
On-time · 90 days
98%
41/42 runs under 3 min
RT coverage: 42 full · 0 partial · 0 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

  • Sat 24 Oct Max en route +3 min · last fix heading to Olten +3 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

Last 90 days, 42 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
19:21on time on time
19:25≈ on time ≈ on time
19:27≈ on time ≈ on time
19:32≈ on time ≈ +1 min
19:36≈ on time ≈ +1 min
19:40on 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
Wed 11 NovOlten 20:390 min—
Tue 10 NovOlten 20:39−1 min—
Sun 8 NovOlten 20:390 min—
Sat 7 NovOlten 20:42+2 min+2 min
Fri 6 NovOlten 20:39−1 min—
Thu 5 NovOlten 20:390 min—
Wed 4 NovOlten 20:390 min—
Tue 3 NovOlten 20:42+1 min—
Mon 2 NovOlten 20:39−1 min—
Sun 1 NovOlten 20:39−1 min—
Sat 31 OctOlten 20:410 min—
Fri 30 OctOlten 20:410 min—
Thu 29 OctOlten 20:410 min—
Wed 28 OctOlten 20:410 min—
Tue 27 OctOlten 20:410 min—
Mon 26 OctOlten 20:410 min—
Sun 25 OctOlten 20:410 min—
Sat 24 OctOlten 20:44+3 min+3 min
Fri 23 OctOlten 20:43+2 min+2 min
Thu 22 OctOlten 20:410 min—
Wed 21 OctOlten 20:410 min—
Tue 20 OctOlten 20:410 min—
Mon 19 OctOlten 20:410 min—
Sun 18 OctOlten 20:410 min—
Sat 17 OctOlten 20:400 min—
Fri 16 OctOlten 20:42+1 min—
Thu 15 OctOlten 20:410 min—
Wed 14 OctOlten 20:43+1 min+4 min
Tue 13 OctOlten 20:42+1 min+1 min
Mon 12 OctOlten 20:400 min—