S42 6631 Burgdorf – Thun
Alerts for train 6631
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S42.
✓ Today’s run finished
Today it reached Thun at 18:58 +1 min
- Burgdorf17:52
- Hasle-Rüegsau18:01
- Biglen18:15
- Stalden i.E.18:37
- Brenzikofen18:44
- Steffisburg18:52
- Thun18:57
Next service: tomorrow 17:52 from Burgdorf · Fri 6 Nov
Last 30 days
Arrival delay at Thun, in minutes. One bar per run.
- On time (<3 min)
- 3–10 min
- 10–30 min
- 30+ min
- Partial coverage
- No data
Worst days
- Wed 21 Oct Max en route +3 min · last fix heading to Thun +3 min
Distribution · 90 days
36 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 3% · 1
- On time 94% · 34
- 3–10 min 3% · 1
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=6
- 80% W n=5
- 100% T n=5
- 100% F n=4
- 100% S n=6
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (16 stops).
Last 90 days, 36 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 |
|---|---|---|---|
| 17:52 | on time | on time | |
| 17:54 | ≈ on time | ≈ on time | |
| 17:56 | ≈ on time | ≈ on time | |
| 18:01 / 18:02 | ≈ on time | ≈ on time | |
| 18:10 / 18:11 | ≈ on time | ≈ +1 min | |
| 18:15 | ≈ on time | ≈ +1 min | |
| 18:18 | ≈ on time | ≈ +1 min | |
| 18:23 / 18:36 | ≈ on time | ≈ +1 min | |
| 18:37 | ≈ +1 min | ≈ +2 min | |
| 18:41 | ≈ +1 min | ≈ +2 min | |
| 18:44 | ≈ +1 min | ≈ +2 min | |
| 18:48 | ≈ +1 min | ≈ +2 min | |
| 18:50 | ≈ +1 min | ≈ +2 min | |
| 18:52 | ≈ +1 min | ≈ +2 min | |
| 18:53 | ≈ +1 min | ≈ +2 min | |
| 18:57 | +1 min | +3 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 | Thun 18:59 | +1 min | +1 min |
| Wed 4 Nov | Thun 18:58 | 0 min | — |
| Tue 3 Nov | Thun 18:58 | 0 min | — |
| Mon 2 Nov | Thun 18:59 | +1 min | — |
| Sun 1 Nov | Thun 18:58 | 0 min | — |
| Sat 31 Oct | Thun 18:57 | −1 min | — |
| Fri 30 Oct | Thun 18:59 | +1 min | — |
| Thu 29 Oct | Thun 18:58 | 0 min | — |
| Wed 28 Oct | Thun 19:00 | +2 min | +2 min |
| Tue 27 Oct | Thun 18:58 | 0 min | — |
| Mon 26 Oct | Thun 18:58 | 0 min | — |
| Sun 25 Oct | Thun 18:59 | +2 min | +2 min |
| Sat 24 Oct | Thun 18:58 | 0 min | — |
| Fri 23 Oct | Thun 19:01 | +3 min | +3 min |
| Thu 22 Oct | Thun 19:01 | +2 min | +2 min |
| Wed 21 Oct | Thun 19:01 | +3 min | +3 min |
| Tue 20 Oct | Thun 19:00 | +2 min | +2 min |
| Mon 19 Oct | Thun 18:58 | +1 min | — |
| Sun 18 Oct | Thun 18:58 | 0 min | — |
| Sat 17 Oct | Thun 18:59 | +1 min | — |
| Fri 16 Oct | Thun 19:01 | +2 min | +2 min |
| Thu 15 Oct | Thun 19:01 | +3 min | +3 min |
| Wed 14 Oct | Thun 19:00 | +2 min | +2 min |
| Tue 13 Oct | Thun 18:58 | 0 min | — |
| Mon 12 Oct | Thun 18:58 | 0 min | — |
| Sun 11 Oct | Thun 18:57 | −1 min | — |
| Sat 10 Oct | Thun 18:58 | −1 min | — |
| Fri 9 Oct | Thun 19:01 | +2 min | +2 min |
| Thu 8 Oct | Thun 18:57 | −1 min | — |
| Wed 7 Oct | Thun 19:01 | +3 min | +3 min |