S1 15153 Fribourg/Freiburg – Thun
Alerts for train 15153
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line S1.
It has not run yet today
Last recorded run: Wednesday 4 November 0 min
Next service: today 14:12 from Fribourg/Freiburg · Thu 5 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
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 91% · 30
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=5
- 100% T n=5
- 100% W n=6
- 100% T n=4
- 100% F n=4
- 100% S n=4
- 100% S n=5
Stops and timetable
Timetable of the latest run from the operator’s GTFS (20 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 |
|---|---|---|---|
| 14:12 | on time | on time | |
| 14:14 | ≈ on time | ≈ on time | |
| 14:17 / 14:18 | ≈ on time | ≈ on time | |
| 14:22 | ≈ on time | ≈ on time | |
| 14:25 | ≈ on time | ≈ on time | |
| 14:28 / 14:29 | ≈ on time | ≈ on time | |
| 14:31 | ≈ on time | ≈ on time | |
| 14:35 | ≈ on time | ≈ on time | |
| 14:37 | ≈ on time | ≈ on time | |
| 14:39 | ≈ on time | ≈ on time | |
| 14:44 / 14:47 | ≈ on time | ≈ on time | |
| 14:50 | ≈ on time | ≈ on time | |
| 14:53 | ≈ on time | ≈ on time | |
| 14:56 | ≈ on time | ≈ on time | |
| 15:00 | ≈ on time | ≈ on time | |
| 15:03 / 15:04 | ≈ on time | ≈ on time | |
| 15:06 / 15:07 | ≈ on time | ≈ on time | |
| 15:09 | ≈ on time | ≈ on time | |
| 15:11 | ≈ on time | ≈ on time | |
| 15:18 | on time | on time |
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 | Thun 15:19 | 0 min | — |
| Tue 3 Nov | Thun 15:19 | 0 min | — |
| Mon 2 Nov | Thun 15:19 | 0 min | — |
| Sun 1 Nov | Thun 15:19 | 0 min | — |
| Sat 31 Oct | Thun 15:18 | −1 min | — |
| Fri 30 Oct | Thun 15:18 | −1 min | +14 min |
| Thu 29 Oct | Thun 15:19 | 0 min | — |
| Wed 28 Oct | Thun 15:18 | −1 min | — |
| Tue 27 Oct | Thun 15:19 | 0 min | — |
| Mon 26 Oct | Thun 15:19 | −1 min | — |
| Sun 25 Oct | Thun 15:18 | −1 min | — |
| Sat 24 Oct | Thun 15:19 | 0 min | — |
| Fri 23 Oct | Thun 15:19 | 0 min | — |
| Thu 22 Oct | Thun 15:19 | −1 min | — |
| Wed 21 Oct | Thun 15:19 | 0 min | — |
| Tue 20 Oct | Thun 15:19 | 0 min | — |
| Mon 19 Oct | Thun 15:19 | 0 min | — |
| Sun 18 Oct | Thun 15:18 | −1 min | — |
| Sat 17 Oct | Thun 15:20 | +1 min | +1 min |
| Fri 16 Oct | Thun 15:19 | 0 min | — |
| Thu 15 Oct | Thun 15:18 | −1 min | — |
| Wed 14 Oct | Thun 15:18 | −1 min | — |
| Tue 13 Oct | Thun 15:18 | −1 min | — |
| Mon 12 Oct | Thun 15:18 | −1 min | — |
| Sun 11 Oct | Thun 15:18 | −1 min | — |
| Sat 10 Oct | Thun 15:18 | −1 min | — |
| Fri 9 Oct | Thun 15:19 | +1 min | — |
| Thu 8 Oct | Thun 15:20 | +1 min | — |
| Wed 7 Oct | Thun 15:18 | 0 min | — |
| Tue 6 Oct | Thun 15:19 | 0 min | — |