S23 8477 Langenthal → Baden

View line S23

Langenthal 19:44 → Baden 20:55 Daily 1 h 11 min · 18 stops SBB CFF FFS

S23 8477 Langenthal–Baden: final delay under 3 min on 29 of its 30 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 22 Nov 2026, 21:12 (GMT+1).

✓ Today’s run finished

Today it reached Baden at 20:55 −1 min

  1. Langenthal19:44
  2. Rothrist19:55
  3. Dulliken20:09
  4. Aarau20:18
  5. Lenzburg20:27
  6. Lupfig20:39
  7. Baden20:55

Next service: tomorrow 19:44 from Langenthal · Mon 23 Nov

Next departure 19:44 tomorrow · Langenthal
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
95%
59/62 runs under 3 min
RT coverage: 62 full · 0 partial · 3 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: +2 min

Last 30 days

Arrival delay at Baden, in minutes. One bar per run.

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

Worst days

  • Wed 14 Oct Max en route +26 min · last fix heading to Baden +26 min
  • Mon 9 Nov Max en route +4 min · last fix heading to Baden +4 min
  • Fri 23 Oct Max en route +3 min · last fix heading to Baden +3 min

Distribution · 90 days

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

  • Early 10% · 6
  • On time 85% · 53
  • 3–10 min 3% · 2
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 88% M n=8
  • 100% T n=7
  • 90% W n=10
  • 100% T n=9
  • 89% F n=9
  • 100% S n=9
  • 100% S n=10

Stops and timetable

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

Last 90 days, 62 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:44on time on time
19:48≈ on time ≈ on time
19:50≈ on time ≈ on time
19:55 / 19:56≈ on time ≈ on time
19:59≈ on time ≈ on time
20:03 / 20:05≈ on time ≈ on time
20:09≈ on time ≈ +1 min
20:11≈ on time ≈ +1 min
20:14≈ on time ≈ +1 min
20:18≈ on time ≈ +1 min
20:23≈ on time ≈ +1 min
20:27 / 20:29≈ on time ≈ +1 min
20:32 / 20:34≈ on time ≈ +1 min
20:37≈ on time ≈ +1 min
20:39 / 20:40≈ on time ≈ +1 min
20:44 / 20:45≈ on time ≈ +1 min
20:49≈ on time ≈ +2 min
20:55on 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
Sun 22 NovBaden 20:54−1 min—
Sat 21 NovBaden 20:54−1 min—
Fri 20 NovBaden 20:57+1 min+1 min
Thu 19 NovBaden 20:57+1 min—
Wed 18 NovBaden 20:540 min—
Tue 17 NovBaden 20:57+1 min+1 min
Mon 16 NovBaden 20:58+3 min+3 min
Sun 15 NovBaden 20:54−1 min—
Sat 14 NovBaden 20:550 min—
Fri 13 NovBaden 20:57+1 min+1 min
Thu 12 NovBaden 20:59+2 min+2 min
Wed 11 NovBaden 20:540 min—
Tue 10 NovBaden 20:54−1 min—
Mon 9 NovBaden 20:59+4 min+4 min
Sun 8 NovBaden 20:54−1 min—
Sat 7 NovBaden 20:54−1 min—
Fri 6 NovBaden 20:57+2 min+2 min
Thu 5 NovBaden 20:54−1 min—
Wed 4 NovBaden 20:57+1 min—
Tue 3 NovBaden 20:54−1 min—
Mon 2 NovBaden 20:57+1 min—
Sun 1 NovBaden 20:54−1 min—
Sat 31 OctBaden 20:55−1 min—
Fri 30 OctBaden 20:58+2 min+2 min
Thu 29 OctBaden 20:55−1 min—
Wed 28 OctBaden 20:57+1 min+1 min
Tue 27 OctBaden 20:570 min—
Mon 26 OctBaden 20:57+1 min—
Sun 25 OctBaden 20:560 min—
Sat 24 OctBaden 20:55−1 min—