S23 8417 Langenthal – Othmarsingen

View line S23

Langenthal 23:44 → Othmarsingen 00:32 Mon, Tue, Wed, Thu, Fri 0 h 48 min · 13 stops SBB CFF FFS

It has not run yet today

Last recorded run: Monday 16 November −1 min

Next service: today 23:44 from Langenthal · Tue 17 Nov

Next departure 23:44 today · Langenthal
On-time · 30 days
100%
20/20 runs under 3 min
RT coverage: 17 full · 3 partial · 1 no data
On-time · 90 days
98%
42/43 runs under 3 min
RT coverage: 40 full · 3 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Othmarsingen, 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 26 Sept Max en route +3 min · last fix heading to Lenzburg +3 min

Distribution · 90 days

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

  • Early 19% · 8
  • On time 79% · 34
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=8
  • 100% F n=9
  • 67% S n=3
  • 100% S n=2

Stops and timetable

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

Last 90 days, 43 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
23:44on time on time
23:48≈ on time ≈ on time
23:50≈ on time ≈ on time
23:55 / 23:56≈ on time ≈ on time
23:59≈ on time ≈ on time
00:03 / 00:05≈ on time ≈ on time
00:09≈ on time ≈ +1 min
00:11≈ on time ≈ +1 min
00:14≈ on time ≈ +1 min
00:18≈ on time ≈ +1 min
00:23≈ on time ≈ +1 min
00:27 / 00:29≈ on time ≈ +1 min
00:32on 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
Mon 16 NovBaden 05:54Partial coverage−1 min—
Fri 13 NovBaden 05:54Partial coverage−2 min—
Thu 12 NovBaden 05:54Partial coverage−1 min—
Wed 11 NovBaden 05:54−1 min—
Tue 10 NovBaden 05:57+1 min+1 min
Mon 9 NovBaden 05:54−1 min—
Fri 6 NovBaden 05:54−1 min—
Thu 5 NovBaden 05:540 min—
Wed 4 NovBaden 05:54−1 min—
Tue 3 NovBaden 05:54−1 min—
Mon 2 NovBaden 05:57+1 min+1 min
Fri 30 OctBaden 05:55−1 min—
Thu 29 OctBaden 05:55−1 min—
Wed 28 OctBaden 05:59+3 min+3 min
Tue 27 OctBaden 05:560 min—
Mon 26 OctBaden 05:55−1 min—
Fri 23 OctBaden 05:54−2 min—
Thu 22 OctBaden 05:56−1 min—
Wed 21 OctBaden 05:55−1 min—
Tue 20 OctBaden 05:550 min—
Mon 19 OctBaden 05:56No data—
Fri 16 OctBaden 05:54−2 min—
Thu 15 OctBaden 05:560 min—
Wed 14 OctBaden 05:560 min—
Tue 13 OctBaden 05:550 min—
Mon 12 OctBaden 05:57+1 min—
Fri 9 OctBaden 05:560 min—
Thu 8 OctBaden 05:560 min—
Wed 7 OctBaden 05:57+1 min+1 min
Tue 6 OctBaden 05:560 min—