R41 253 Visp – Zermatt

View line R41

Visp 17:11 → Zermatt 18:17 Daily 1 h 06 min · 8 stops MGB

It has not run yet today

Last recorded run: Tuesday 10 November +1 min

Next service: today 17:11 from Visp · Wed 11 Nov

Next departure 17:11 today · Visp
On-time · 30 days
83%
24/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
81%
42/52 runs under 3 min
RT coverage: 52 full · 0 partial · 2 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 min

Last 30 days

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

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

Worst days

  • Sat 3 Oct Max en route +13 min · last fix heading to Zermatt +12 min
  • Sun 25 Oct Max en route +7 min · last fix heading to Glovelier +4 min
  • Sun 4 Oct Max en route +4 min · last fix heading to Zermatt +4 min
  • Sun 8 Nov Max en route +4 min · last fix heading to Glovelier +4 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Zermatt +4 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 81% · 42
  • 3–10 min 17% · 9
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 89% T n=9
  • 89% W n=9
  • 83% T n=6
  • 100% F n=6
  • 50% S n=8
  • 57% S n=7

Stops and timetable

Timetable of the latest run from the operator’s GTFS (8 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
17:111 min early +1 min
17:20 / 17:21≈ on time ≈ +1 min
17:28≈ on time ≈ +2 min
17:37 / 17:38≈ on time ≈ +2 min
17:48≈ +1 min ≈ +2 min
17:56 / 17:57≈ +1 min ≈ +2 min
18:02≈ +1 min ≈ +2 min
18:17+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

DateLast stopFinalMax
Tue 10 NovZermatt 18:18+1 min+2 min
Mon 9 NovZermatt 18:18+1 min+3 min
Sun 8 NovGlovelier 15:19+4 min+4 min
Sat 7 NovEchallens 18:070 min+3 min
Fri 6 NovEchallens 18:08+1 min+2 min
Thu 5 NovEchallens 18:09+1 min+2 min
Wed 4 NovEchallens 18:09+1 min+3 min
Tue 3 NovEchallens 18:080 min+3 min
Mon 2 NovEchallens 18:09+2 min+4 min
Sun 1 NovGlovelier 15:21+2 min+2 min
Sat 31 OctEchallens 18:080 min+3 min
Fri 30 OctEchallens 18:09+1 min+2 min
Thu 29 OctEchallens 18:080 min+4 min
Wed 28 OctEchallens 18:10+1 min+2 min
Tue 27 OctEchallens 18:09+1 min+2 min
Mon 26 OctEchallens 18:10+2 min+2 min
Sun 25 OctGlovelier 15:22+4 min+7 min
Sat 24 OctEchallens 18:08+4 min+4 min
Fri 23 OctEchallens 18:080 min+3 min
Thu 22 OctEchallens 18:08+3 min+3 min
Wed 21 OctEchallens 18:09+1 min+9 min
Tue 20 OctEchallens 18:080 min—
Mon 19 OctEchallens 18:07−1 min+2 min
Sun 18 OctGlovelier 15:190 min+3 min
Sat 17 OctEchallens 18:08+3 min+3 min
Fri 16 OctEchallens 18:090 min+4 min
Thu 15 OctEchallens 18:080 min+4 min
Wed 14 OctEchallens 18:09+2 min+2 min
Tue 13 OctEchallens 18:08+2 min+2 min
Mon 12 OctEchallens 18:080 min+2 min