S3 15342 Biel/Bienne – Belp
Alerts for train 15342
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: Thursday 5 November No data
Next service: today 11:24 from Biel/Bienne · Fri 6 Nov
Last 30 days
Arrival delay at Belp, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Fri 16 Oct Max en route +6 min · last fix heading to Belp +6 min
Distribution · 90 days
33 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 9% · 3
- On time 88% · 29
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=2
- 100% T n=7
- 100% W n=7
- 100% T n=2
- 80% F n=5
- 100% S n=5
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (18 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 |
|---|---|---|---|
| 11:24 | on time | on time | |
| 11:27 | ≈ on time | ≈ on time | |
| 11:30 | ≈ on time | ≈ on time | |
| 11:32 | ≈ on time | ≈ on time | |
| 11:36 / 11:37 | ≈ on time | ≈ on time | |
| 11:40 | ≈ on time | ≈ on time | |
| 11:43 | ≈ on time | ≈ on time | |
| 11:48 | ≈ on time | ≈ on time | |
| 11:51 | ≈ on time | ≈ on time | |
| 11:55 | ≈ on time | ≈ +1 min | |
| 12:00 / 12:02 | ≈ on time | ≈ +1 min | |
| 12:06 | ≈ on time | ≈ +1 min | |
| 12:08 | ≈ on time | ≈ +1 min | |
| 12:11 | ≈ on time | ≈ +1 min | |
| 12:13 | ≈ on time | ≈ +1 min | |
| 12:15 | ≈ on time | ≈ +1 min | |
| 12:18 | ≈ on time | ≈ +1 min | |
| 12:21 | 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 |
|---|---|---|---|
| Thu 5 Nov | Belp 12:22 | No data | — |
| Wed 4 Nov | Belp 12:19 | 0 min | — |
| Tue 3 Nov | Belp 12:19 | 0 min | — |
| Mon 2 Nov | Belp 12:22 | No data | — |
| Sun 1 Nov | Belp 12:21 | 0 min | — |
| Sat 31 Oct | Belp 12:21 | 0 min | — |
| Fri 30 Oct | Belp 12:21 | −1 min | — |
| Thu 29 Oct | Belp 12:22 | No data | — |
| Wed 28 Oct | Belp 12:22 | −1 min | — |
| Tue 27 Oct | Belp 12:23 | +1 min | +1 min |
| Mon 26 Oct | Belp 12:23 | No data | — |
| Sun 25 Oct | Belp 12:21 | 0 min | — |
| Sat 24 Oct | Belp 12:22 | 0 min | — |
| Fri 23 Oct | Belp 12:22 | 0 min | — |
| Thu 22 Oct | Belp 12:22 | No data | — |
| Wed 21 Oct | Belp 12:22 | 0 min | — |
| Tue 20 Oct | Belp 12:21 | −1 min | — |
| Mon 19 Oct | Belp 12:22 | No data | — |
| Sun 18 Oct | Belp 12:22 | −1 min | — |
| Sat 17 Oct | Belp 12:22 | 0 min | — |
| Fri 16 Oct | Belp 12:27 | +6 min | +6 min |
| Thu 15 Oct | Belp 12:22 | No data | — |
| Wed 14 Oct | Belp 12:22 | +1 min | — |
| Tue 13 Oct | Belp 12:23 | 0 min | — |
| Mon 12 Oct | Belp 12:22 | No data | — |
| Sun 11 Oct | Belp 12:21 | −1 min | — |
| Sat 10 Oct | Belp 12:22 | 0 min | — |
| Fri 9 Oct | Belp 12:22 | +1 min | — |
| Thu 8 Oct | Belp 12:22 | +1 min | +1 min |
| Wed 7 Oct | Belp 12:23 | +1 min | +1 min |