S23 8484 Baden – Othmarsingen
Alerts for train 8484
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S23.
It has not run yet today
Last recorded run: Thursday 5 November −1 min
Next service: today 22:04 from Baden · Fri 6 Nov
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
- Tue 13 Oct Max en route +5 min · last fix heading to Langenthal +4 min
- Sun 25 Oct Max en route +3 min · last fix heading to Langenthal +3 min
Distribution · 90 days
45 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 4% · 2
- On time 91% · 41
- 3–10 min 4% · 2
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=8
- 86% T n=7
- 100% W n=7
- 100% T n=6
- 100% F n=7
- 100% S n=5
- 80% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (6 stops).
Last 90 days, 45 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.
| Stop | Sched. | Usually | 9 days in 10 |
|---|---|---|---|
| 22:04 | on time | +1 min | |
| 22:08 | ≈ on time | ≈ +1 min | |
| 22:13 / 22:14 | ≈ on time | ≈ +1 min | |
| 22:18 | ≈ on time | ≈ +1 min | |
| 22:20 | ≈ on time | ≈ +1 min | |
| 22:25 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Thu 5 Nov | Othmarsingen 22:23 | −1 min | — |
| Wed 4 Nov | Othmarsingen 22:24 | −1 min | — |
| Tue 3 Nov | Othmarsingen 22:24 | −1 min | — |
| Mon 2 Nov | Othmarsingen 22:24 | No data | — |
| Sun 1 Nov | Langenthal 23:14 | 0 min | — |
| Sat 31 Oct | Langenthal 23:15 | +1 min | — |
| Fri 30 Oct | Langenthal 23:15 | 0 min | — |
| Thu 29 Oct | Langenthal 23:14 | −1 min | — |
| Wed 28 Oct | Langenthal 23:17 | +2 min | +2 min |
| Tue 27 Oct | Langenthal 23:15 | 0 min | — |
| Mon 26 Oct | Langenthal 23:15 | −1 min | — |
| Sun 25 Oct | Langenthal 23:18 | +3 min | +3 min |
| Sat 24 Oct | Langenthal 23:16 | +2 min | +2 min |
| Fri 23 Oct | Langenthal 23:15 | 0 min | — |
| Thu 22 Oct | Langenthal 23:15 | 0 min | — |
| Wed 21 Oct | Langenthal 23:16 | +1 min | — |
| Tue 20 Oct | Langenthal 23:15 | 0 min | — |
| Mon 19 Oct | Langenthal 23:16 | +1 min | +1 min |
| Sun 18 Oct | Langenthal 23:17 | +2 min | +2 min |
| Sat 17 Oct | Langenthal 23:16 | +1 min | — |
| Fri 16 Oct | Langenthal 23:17 | +2 min | +2 min |
| Thu 15 Oct | Langenthal 23:16 | +1 min | — |
| Wed 14 Oct | Langenthal 23:16 | 0 min | — |
| Tue 13 Oct | Langenthal 23:19 | +4 min | +5 min |
| Mon 12 Oct | Langenthal 23:16 | +1 min | — |
| Sun 11 Oct | Langenthal 23:14 | −1 min | — |
| Sat 10 Oct | Langenthal 23:15 | −1 min | — |
| Fri 9 Oct | Langenthal 23:17 | +2 min | +2 min |
| Thu 8 Oct | Langenthal 23:16 | +1 min | — |
| Wed 7 Oct | Langenthal 23:17 | +1 min | +1 min |