S23 8456 Baden → Olten

View line S23

Baden 15:04 → Olten 15:53 Daily 0 h 49 min · 13 stops SBB CFF FFS

S23 8456 Baden–Olten: final delay under 3 min on 28 of its 30 runs with data in the last 30 days (93%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 16:09 (GMT+1).

✓ Today’s run finished

Today it reached Olten at 15:53 0 min

  1. Baden15:04
  2. Brugg AG15:13
  3. Birr15:20
  4. Lenzburg15:30
  5. Aarau15:40
  6. Däniken SO15:46
  7. Olten15:53

Next service: tomorrow 15:04 from Baden · Mon 23 Nov

Next departure 15:04 tomorrow · Baden
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
96%
53/55 runs under 3 min
RT coverage: 55 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 +4 min · last fix heading to Langenthal +4 min
  • Wed 18 Nov Max en route +4 min · last fix heading to Langenthal +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 96% · 53
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 55 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
15:04on time on time
15:08≈ on time ≈ on time
15:13 / 15:14≈ on time ≈ on time
15:18≈ on time ≈ on time
15:20≈ on time ≈ on time
15:25≈ on time ≈ on time
15:30 / 15:31≈ on time ≈ +1 min
15:35≈ on time ≈ +1 min
15:40≈ on time ≈ +1 min
15:44≈ on time ≈ +1 min
15:46≈ on time ≈ +1 min
15:49≈ on time ≈ +1 min
15:53on 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
Sun 22 NovOlten 15:540 min—
Sat 21 NovOlten 15:54+1 min—
Fri 20 NovLangenthal 16:140 min—
Thu 19 NovLangenthal 16:14+1 min—
Wed 18 NovLangenthal 16:18+4 min+4 min
Tue 17 NovLangenthal 16:140 min—
Mon 16 NovLangenthal 16:140 min—
Sun 15 NovLangenthal 16:140 min—
Sat 14 NovLangenthal 16:140 min—
Fri 13 NovLangenthal 16:140 min—
Thu 12 NovLangenthal 16:130 min—
Wed 11 NovLangenthal 16:140 min—
Tue 10 NovLangenthal 16:14+1 min—
Mon 9 NovLangenthal 16:140 min—
Sun 8 NovLangenthal 16:14+1 min—
Sat 7 NovLangenthal 16:14−1 min—
Fri 6 NovLangenthal 16:18+3 min+3 min
Thu 5 NovLangenthal 16:140 min—
Wed 4 NovLangenthal 16:140 min—
Tue 3 NovLangenthal 16:140 min—
Mon 2 NovLangenthal 16:140 min—
Sun 1 NovLangenthal 16:150 min—
Sat 31 OctLangenthal 16:14−1 min—
Fri 30 OctLangenthal 16:150 min—
Thu 29 OctLangenthal 16:150 min—
Wed 28 OctLangenthal 16:15−1 min—
Tue 27 OctLangenthal 16:150 min—
Mon 26 OctLangenthal 16:14−1 min—
Sun 25 OctLangenthal 16:24+1 min+1 min
Sat 24 OctLangenthal 16:27+4 min+4 min