R41 221 Visp – Zermatt

View line R41

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

✓ Today’s run finished

Today it reached Zermatt at 10:17 0 min

  1. Visp09:11
  2. Stalden-Saas09:20
  3. Kalpetran09:28
  4. Herbriggen09:48
  5. Randa09:56
  6. Täsch10:02
  7. Zermatt10:17

Next service: tomorrow 09:11 from Visp · Thu 19 Nov

Next departure 09:11 tomorrow · Visp
On-time · 30 days
86%
25/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
90%
53/59 runs under 3 min
RT coverage: 59 full · 0 partial · 1 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: 0 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +4 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

  • Tue 3 Nov Max en route +9 min · last fix heading to Ponte Tresa +9 min
  • Fri 30 Oct Max en route +7 min · last fix heading to Ponte Tresa +7 min
  • Thu 29 Oct Max en route +6 min · last fix heading to Ponte Tresa +5 min
  • Fri 9 Oct Max en route +4 min · last fix heading to Ponte Tresa +4 min
  • Fri 16 Oct Max en route +4 min · last fix heading to Ponte Tresa +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 90% · 53
  • 3–10 min 10% · 6
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=10
  • 86% T n=7
  • 100% W n=9
  • 86% T n=7
  • 56% F n=9
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 59 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
09:11on time on time
09:20 / 09:21≈ on time ≈ +1 min
09:28≈ on time ≈ +1 min
09:37 / 09:38≈ on time ≈ +1 min
09:48≈ on time ≈ +2 min
09:56 / 09:57≈ on time ≈ +2 min
10:02≈ on time ≈ +2 min
10: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
Wed 18 NovZermatt 10:180 min+3 min
Tue 17 NovPonte Tresa 22:04+1 min+4 min
Mon 16 NovPonte Tresa 22:040 min+5 min
Sun 15 NovPonte Tresa 22:040 min—
Sat 14 NovPonte Tresa 22:04+1 min—
Fri 13 NovPonte Tresa 22:040 min+2 min
Thu 12 NovPonte Tresa 22:08+1 min+2 min
Wed 11 NovPonte Tresa 22:040 min+5 min
Tue 10 NovPonte Tresa 22:040 min+3 min
Mon 9 NovPonte Tresa 22:040 min—
Sun 8 NovPonte Tresa 22:07+1 min—
Sat 7 NovPonte Tresa 22:040 min—
Fri 6 NovPonte Tresa 22:04+3 min+3 min
Thu 5 NovPonte Tresa 22:040 min+8 min
Wed 4 NovPonte Tresa 22:04+3 min+9 min
Tue 3 NovPonte Tresa 22:04+9 min+9 min
Mon 2 NovPonte Tresa 22:07+1 min—
Sun 1 NovPonte Tresa 22:070 min—
Sat 31 OctPonte Tresa 22:07+1 min—
Fri 30 OctPonte Tresa 22:13+7 min+7 min
Thu 29 OctPonte Tresa 22:11+5 min+6 min
Wed 28 OctPonte Tresa 22:060 min+3 min
Tue 27 OctPonte Tresa 22:060 min+10 min
Mon 26 OctPonte Tresa 22:07+1 min+1 min
Sun 25 OctPonte Tresa 22:06No data—
Sat 24 OctPonte Tresa 22:06+1 min—
Fri 23 OctPonte Tresa 22:060 min+2 min
Thu 22 OctPonte Tresa 22:060 min+3 min
Wed 21 OctPonte Tresa 22:060 min+10 min
Tue 20 OctPonte Tresa 22:060 min—