RE1 4267 Spiez – Brig
Alerts for train 4267
Alerts are saved per line, not per trip id, so they keep working when the operator changes the timetable. This train runs on line RE1.
✓ Today’s run finished
Today it reached Brig at 12:22 −7 min
- Spiez11:12
- Reichenbach im Kandertal11:19
- Frutigen11:24
- Goppenstein11:52
- Ausserberg12:04
- Eggerberg12:07
- Brig12:22
Next service: tomorrow 11:12 from Spiez · Sat 14 Nov
Last 30 days
Arrival delay at Brig, 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
43 runs with a known final delay. On time = under 3 min, the same cut the map uses.
- Early 84% · 36
- On time 16% · 7
- 3–10 min 0% · 0
- 10–30 min 0% · 0
- 30+ min 0% · 0
On-time by weekday
- 100% M n=4
- 100% T n=7
- 100% W n=8
- 100% T n=2
- 100% F n=8
- 100% S n=7
- 100% S n=7
Stops and timetable
Timetable of the latest run from the operator’s GTFS (11 stops).
Last 90 days, 43 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:12 | on time | on time | |
| 11:17 | ≈ on time | ≈ on time | |
| 11:19 | ≈ on time | ≈ on time | |
| 11:24 / 11:25 | ≈ 1 min early | ≈ on time | |
| 11:40 / 11:41 | ≈ 2 min early | ≈ on time | |
| 11:52 | ≈ 3 min early | ≈ on time | |
| 11:56 | ≈ 3 min early | ≈ on time | |
| 12:04 | ≈ 3 min early | ≈ on time | |
| 12:07 | ≈ 4 min early | ≈ on time | |
| 12:10 | ≈ 4 min early | ≈ on time | |
| 12:22 | 5 min early | 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 |
|---|---|---|---|
| Fri 13 Nov | Brig 12:17 | −7 min | — |
| Thu 12 Nov | Brig 12:23 | No data | — |
| Wed 11 Nov | Brig 12:19 | −2 min | — |
| Tue 10 Nov | Brig 12:24 | 0 min | — |
| Mon 9 Nov | Brig 12:23 | No data | — |
| Sun 8 Nov | Brig 12:19 | 0 min | — |
| Sat 7 Nov | Brig 12:17 | −6 min | — |
| Fri 6 Nov | Brig 12:17 | −6 min | — |
| Thu 5 Nov | Brig 12:23 | No data | — |
| Wed 4 Nov | Brig 12:18 | −5 min | — |
| Tue 3 Nov | Brig 12:19 | −1 min | — |
| Mon 2 Nov | Brig 12:23 | No data | — |
| Sun 1 Nov | Brig 12:22 | −1 min | — |
| Sat 31 Oct | Brig 12:19 | −4 min | — |
| Fri 30 Oct | Brig 12:21 | −2 min | — |
| Thu 29 Oct | Brig 12:23 | No data | — |
| Wed 28 Oct | Brig 12:19 | −5 min | — |
| Tue 27 Oct | Brig 12:17 | −6 min | — |
| Mon 26 Oct | Brig 12:24 | No data | — |
| Sun 25 Oct | Brig 12:19 | −4 min | — |
| Sat 24 Oct | Brig 12:20 | −3 min | — |
| Fri 23 Oct | Brig 12:17 | −5 min | — |
| Thu 22 Oct | Brig 12:23 | No data | — |
| Wed 21 Oct | Brig 12:17 | −6 min | — |
| Tue 20 Oct | Brig 12:18 | −6 min | — |
| Mon 19 Oct | Brig 12:23 | No data | — |
| Sun 18 Oct | Brig 12:18 | −5 min | — |
| Sat 17 Oct | Brig 12:17 | −6 min | — |
| Fri 16 Oct | Brig 12:19 | −5 min | — |
| Thu 15 Oct | Brig 12:23 | No data | — |