S23 8453 Langenthal – Baden

View line S23

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

✓ Today’s run finished

Today it reached Baden at 14:55 −1 min

  1. Langenthal13:44
  2. Rothrist13:55
  3. Dulliken14:09
  4. Aarau14:18
  5. Lenzburg14:27
  6. Lupfig14:39
  7. Baden14:55

Next service: tomorrow 13:44 from Langenthal · Thu 12 Nov

Next departure 13:44 tomorrow · Langenthal
On-time · 30 days
100%
27/27 runs under 3 min
RT coverage: 27 full · 0 partial · 3 no data
On-time · 90 days
100%
49/49 runs under 3 min
RT coverage: 49 full · 0 partial · 5 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 Baden, 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

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

  • Early 10% · 5
  • On time 90% · 44
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

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