S3 17346 Olten – Laufen
Alerts for train 17346
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S3.
It has not run yet today
Last recorded run: Wednesday 4 November +1 min
Next service: today 12:48 from Olten · Thu 5 Nov
Last 30 days
Arrival delay at Laufen, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Mon 5 Oct Max en route +5 min · last fix heading to Laufen +5 min
Distribution · 90 days
33 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 97% · 32
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 50% M n=2
- 100% T n=7
- 100% W n=6
- 100% T n=3
- 100% F n=5
- 100% S n=5
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (19 stops).
Last 90 days, 33 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 |
|---|---|---|---|
| 12:48 | on time | on time | |
| 12:55 | ≈ on time | ≈ on time | |
| 12:58 | ≈ on time | ≈ on time | |
| 13:02 | ≈ on time | ≈ on time | |
| 13:04 | ≈ on time | ≈ on time | |
| 13:06 | ≈ on time | ≈ on time | |
| 13:10 | ≈ on time | ≈ on time | |
| 13:13 | ≈ on time | ≈ on time | |
| 13:16 / 13:17 | ≈ on time | ≈ on time | |
| 13:20 | ≈ on time | ≈ on time | |
| 13:26 / 13:38 | ≈ on time | ≈ on time | |
| 13:41 | ≈ on time | ≈ +1 min | |
| 13:44 | ≈ on time | ≈ +1 min | |
| 13:48 | ≈ on time | ≈ +1 min | |
| 13:51 | ≈ on time | ≈ +1 min | |
| 13:53 | ≈ on time | ≈ +1 min | |
| 13:56 / 13:58 | ≈ on time | ≈ +1 min | |
| 14:03 | ≈ on time | ≈ +1 min | |
| 14:07 | on 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
| Date | Last stop | Final | Max |
|---|---|---|---|
| Wed 4 Nov | Laufen 14:08 | +1 min | — |
| Tue 3 Nov | Laufen 14:08 | 0 min | — |
| Mon 2 Nov | Laufen 14:08 | No data | — |
| Sun 1 Nov | Laufen 14:09 | +1 min | — |
| Sat 31 Oct | Laufen 14:07 | 0 min | — |
| Fri 30 Oct | Laufen 14:08 | 0 min | — |
| Thu 29 Oct | Laufen 14:08 | No data | — |
| Wed 28 Oct | Laufen 14:08 | 0 min | — |
| Tue 27 Oct | Laufen 14:08 | 0 min | — |
| Mon 26 Oct | Laufen 14:08 | No data | — |
| Sun 25 Oct | Laufen 14:07 | 0 min | — |
| Sat 24 Oct | Laufen 14:08 | 0 min | — |
| Fri 23 Oct | Laufen 14:08 | 0 min | — |
| Thu 22 Oct | Laufen 14:08 | No data | — |
| Wed 21 Oct | Laufen 14:09 | +1 min | +1 min |
| Tue 20 Oct | Laufen 14:08 | 0 min | — |
| Mon 19 Oct | Laufen 14:08 | No data | — |
| Sun 18 Oct | Laufen 14:08 | 0 min | — |
| Sat 17 Oct | Laufen 14:09 | +1 min | +1 min |
| Fri 16 Oct | Laufen 14:08 | 0 min | — |
| Thu 15 Oct | Laufen 14:08 | No data | — |
| Wed 14 Oct | Laufen 14:09 | +1 min | +1 min |
| Tue 13 Oct | Laufen 14:08 | 0 min | — |
| Mon 12 Oct | Laufen 14:08 | No data | — |
| Sun 11 Oct | Laufen 14:08 | 0 min | — |
| Sat 10 Oct | Laufen 14:09 | 0 min | — |
| Fri 9 Oct | Laufen 14:08 | 0 min | — |
| Thu 8 Oct | Laufen 14:08 | 0 min | — |
| Wed 7 Oct | Laufen 14:08 | 0 min | — |
| Tue 6 Oct | Laufen 14:08 | 0 min | — |