RE1 4262 Domodossola (I) – Spiez

View line RE1

Domodossola (I) 07:58 → Spiez 09:44 Daily 1 h 46 min · 14 stops BLS

✓ Today’s run finished

Today it reached Spiez at 09:44 −1 min

  1. Domodossola (I)07:58
  2. Varzo08:11
  3. Brig08:33
  4. Hohtenn08:54
  5. Kandersteg09:13
  6. Reichenbach im Kandertal09:34
  7. Spiez09:44

Next service: tomorrow 07:58 from Domodossola (I) · Sat 7 Nov

Next departure 07:58 tomorrow · Domodossola (I)
On-time · 30 days
93%
28/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
94%
49/52 runs under 3 min
RT coverage: 52 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Spiez, 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 23 Oct Max en route +4 min · last fix heading to Aarau +3 min
  • Tue 6 Oct Max en route +4 min · last fix heading to Aarau +3 min
  • Sun 1 Nov Max en route +3 min · last fix heading to Spiez +3 min

Distribution · 90 days

52 runs with a known final delay. On time = under 3 min, the same cut the map uses.

  • Early 6% · 3
  • On time 88% · 46
  • 3–10 min 6% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=8
  • 86% T n=7
  • 100% W n=8
  • 100% T n=8
  • 88% F n=8
  • 100% S n=7
  • 83% S n=6

Stops and timetable

Timetable of the latest run from the operator’s GTFS (14 stops).

Last 90 days, 52 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.

StopSched.Usually 9 days in 10
07:58on time on time
08:03≈ on time ≈ on time
08:11≈ on time ≈ on time
08:18≈ on time ≈ on time
08:33 / 08:36≈ on time ≈ on time
08:43≈ on time ≈ on time
08:48≈ on time ≈ on time
08:54≈ on time ≈ +1 min
09:01 / 09:02≈ on time ≈ +1 min
09:13 / 09:14≈ on time ≈ +1 min
09:29 / 09:30≈ on time ≈ +1 min
09:34≈ on time ≈ +1 min
09:35≈ on time ≈ +1 min
09:44on 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

DateLast stopFinalMax
Fri 6 NovSpiez 09:44−1 min—
Thu 5 NovAarau 20:030 min—
Wed 4 NovAarau 20:030 min—
Tue 3 NovAarau 20:030 min—
Mon 2 NovAarau 20:030 min—
Sun 1 NovSpiez 09:48+3 min+3 min
Sat 31 OctAarau 20:02+1 min—
Fri 30 OctAarau 20:020 min—
Thu 29 OctAarau 20:04+1 min—
Wed 28 OctAarau 20:03−1 min—
Tue 27 OctAarau 20:03−1 min—
Mon 26 OctAarau 20:04+1 min—
Sun 25 OctSpiez 09:45+1 min—
Sat 24 OctAarau 20:030 min—
Fri 23 OctAarau 20:06+3 min+4 min
Thu 22 OctAarau 20:030 min+22 min
Wed 21 OctAarau 20:030 min+1 min
Tue 20 OctAarau 20:030 min—
Mon 19 OctAarau 20:03+1 min—
Sun 18 OctSpiez 09:450 min—
Sat 17 OctAarau 20:030 min—
Fri 16 OctAarau 20:030 min+16 min
Thu 15 OctAarau 20:030 min+5 min
Wed 14 OctAarau 20:030 min—
Tue 13 OctAarau 20:040 min—
Mon 12 OctAarau 20:030 min—
Sun 11 OctSpiez 09:45−1 min—
Sat 10 OctAarau 20:03+1 min—
Fri 9 OctAarau 20:040 min—
Thu 8 OctAarau 20:04+1 min+1 min