S31 16332 Münchenbuchsee – Belp
Alerts for train 16332
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S31.
✓ Today’s run finished
Today it reached Belp at 10:06 0 min
- Münchenbuchsee09:33
- Bern Wankdorf09:39
- Bern09:44
- Bern Weissenbühl09:53
- Kehrsatz Nord09:58
- Kehrsatz10:00
- Belp10:06
Next service: Monday 09:33 from Münchenbuchsee · Mon 16 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
- Mon 12 Oct Max en route +6 min · last fix heading to Wabern bei Bern +6 min
Distribution · 90 days
25 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 0% · 0
- On time 96% · 24
- 3–10 min 4% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 88% M n=8
- 100% T n=7
- 100% W n=3
- 100% T n=4
- 100% F n=3
- — S n=0
- — S n=0
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 25 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 |
|---|---|---|---|
| 09:33 | on time | on time | |
| 09:35 / 09:36 | ≈ on time | ≈ on time | |
| 09:39 | ≈ on time | ≈ on time | |
| 09:44 / 09:47 | ≈ on time | ≈ +1 min | |
| 09:51 | ≈ on time | ≈ +1 min | |
| 09:53 | ≈ on time | ≈ +1 min | |
| 09:56 | ≈ on time | ≈ +2 min | |
| 09:58 | ≈ on time | ≈ +2 min | |
| 10:00 | ≈ on time | ≈ +2 min | |
| 10:03 | ≈ on time | ≈ +2 min | |
| 10:06 | 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 |
|---|---|---|---|
| Fri 13 Nov | Belp 10:07 | 0 min | — |
| Thu 12 Nov | Belp 10:07 | 0 min | — |
| Wed 11 Nov | Belp 10:07 | +1 min | — |
| Tue 10 Nov | Belp 10:07 | 0 min | — |
| Mon 9 Nov | Belp 10:09 | +2 min | +2 min |
| Fri 6 Nov | Belp 10:07 | 0 min | — |
| Thu 5 Nov | Belp 10:08 | +1 min | +1 min |
| Wed 4 Nov | Belp 10:07 | No data | — |
| Tue 3 Nov | Belp 10:09 | +3 min | +3 min |
| Mon 2 Nov | Belp 10:08 | +1 min | +1 min |
| Fri 30 Oct | Belp 10:07 | No data | — |
| Thu 29 Oct | Belp 10:07 | No data | — |
| Wed 28 Oct | Belp 10:07 | No data | — |
| Tue 27 Oct | Belp 10:07 | 0 min | — |
| Mon 26 Oct | Münchenbuchsee 11:01 | +2 min | +2 min |
| Fri 23 Oct | Belp 10:07 | No data | — |
| Thu 22 Oct | Belp 10:07 | 0 min | — |
| Wed 21 Oct | Belp 10:07 | No data | — |
| Tue 20 Oct | Belp 10:08 | 0 min | — |
| Mon 19 Oct | Belp 10:07 | 0 min | — |
| Fri 16 Oct | Wabern bei Bern 09:56 | 0 min | — |
| Thu 15 Oct | Wabern bei Bern 09:57 | No data | — |
| Wed 14 Oct | Wabern bei Bern 09:56 | 0 min | — |
| Tue 13 Oct | Wabern bei Bern 09:58 | 0 min | — |
| Mon 12 Oct | Wabern bei Bern 10:03 | +6 min | +6 min |
| Fri 9 Oct | Wabern bei Bern 09:57 | No data | — |
| Thu 8 Oct | Wabern bei Bern 09:58 | +1 min | — |
| Wed 7 Oct | Wabern bei Bern 09:57 | No data | — |
| Tue 6 Oct | Wabern bei Bern 09:57 | 0 min | — |
| Mon 5 Oct | Wabern bei Bern 09:57 | 0 min | — |