RE2 4252 Domodossola (I) – Visp

View line RE2

Domodossola (I) 05:54 → Visp 06:33 Mon, Tue, Wed, Thu, Fri 0 h 39 min · 3 stops BLS

✓ Today’s run finished

Today it reached Visp at 06:33 0 min

  1. Domodossola (I)05:54
  2. Brig06:25
  3. Visp06:33

Next service: tomorrow 05:54 from Domodossola (I) · Fri 6 Nov

Next departure 05:54 tomorrow · Domodossola (I)
On-time · 30 days
92%
24/26 runs under 3 min
RT coverage: 26 full · 0 partial · 0 no data
On-time · 90 days
96%
47/49 runs under 3 min
RT coverage: 49 full · 0 partial · 3 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Visp, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Tue 3 Nov Max en route +6 min · last fix heading to Aarau +6 min
  • Mon 19 Oct Max en route +5 min · last fix heading to Aarau +5 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 94% · 46
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 89% M n=9
  • 89% T n=9
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=10
  • 100% S n=1

Stops and timetable

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

Last 90 days, 49 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
05:54on time on time
06:25 / 06:26≈ on time ≈ +2 min
06:33on 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

DateLast stopFinalMax
Thu 5 NovVisp 06:340 min—
Wed 4 NovAarau 17:34+1 min+1 min
Tue 3 NovAarau 17:39+6 min+6 min
Mon 2 NovAarau 17:34+1 min+1 min
Sat 31 OctAarau 17:34+1 min+1 min
Fri 30 OctAarau 17:35+2 min+2 min
Thu 29 OctAarau 17:35+2 min+2 min
Wed 28 OctAarau 17:330 min+3 min
Tue 27 OctAarau 17:330 min—
Mon 26 OctAarau 17:36+2 min+2 min
Sat 24 OctAarau 17:330 min—
Fri 23 OctAarau 17:330 min—
Thu 22 OctAarau 17:340 min+15 min
Wed 21 OctAarau 17:35+2 min+2 min
Tue 20 OctAarau 17:34+1 min—
Mon 19 OctAarau 17:38+5 min+5 min
Sat 17 OctAarau 17:34+1 min+1 min
Fri 16 OctAarau 17:34+1 min—
Thu 15 OctAarau 17:35+2 min+2 min
Wed 14 OctAarau 17:35+3 min+3 min
Tue 13 OctAarau 17:330 min—
Mon 12 OctAarau 17:330 min—
Sat 10 OctAarau 17:33−1 min—
Fri 9 OctAarau 17:340 min—
Thu 8 OctAarau 17:34+1 min—
Wed 7 OctAarau 17:340 min—
Tue 6 OctAarau 17:34+1 min+1 min
Mon 5 OctAarau 17:330 min—
Sat 3 OctAarau 17:310 min+2 min
Fri 2 OctAarau 17:31+1 min+1 min