R42 344 Zermatt – Fiesch

View line R42

Zermatt 13:06 → Fiesch 15:22 Daily 2 h 16 min · 17 stops MGB

Running now · updated 14:19

Position estimated from the timetable

Between Stalden-Saas and Visp No data

Estimated arrival at Fiesch 15:22 · 18 km/h

  1. Zermatt13:06
  2. Herbriggen13:35
  3. Kalpetran13:57
  4. Stalden-Saas14:06
  5. Visp14:19
  6. Eyholz14:23
  7. Fiesch15:22
On-time · 30 days
100%
29/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
100%
46/46 runs under 3 min
RT coverage: 46 full · 0 partial · 1 no data
Typical delay
+1min
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 Fiesch, 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

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

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

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 100% W n=7
  • 100% T n=6
  • 100% F n=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 46 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 10Today
13:06+1 min +1 minPassed
13:19 / 13:21≈ +1 min ≈ +1 minPassed
13:26 / 13:27≈ +1 min ≈ +1 minPassed
13:35≈ on time ≈ +1 minPassed
13:47≈ +1 min ≈ +1 minPassed
13:57 / 13:58≈ +1 min ≈ +1 minPassed
14:06 / 14:08≈ +1 min ≈ +1 minPassed
14:19 / 14:21≈ +1 min ≈ +1 minNext
14:23≈ +1 min ≈ +1 min
14:32 / 14:48≈ +1 min ≈ +2 min
14:51≈ +1 min ≈ +2 min
14:56 / 14:57≈ +1 min ≈ +2 min
15:03≈ +1 min ≈ +2 min
15:06 / 15:10≈ +1 min ≈ +2 min
15:17≈ +1 min ≈ +2 min
15:20≈ +1 min ≈ +2 min
15:22+1 min +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 19 NovVisp 14:14Partial coverageNo data—
Wed 18 NovSt. Urban 15:29+1 min+4 min
Tue 17 NovSt. Urban 15:29+2 min+3 min
Mon 16 NovSt. Urban 15:29+2 min+2 min
Sun 15 NovSt. Urban 15:29+1 min—
Sat 14 NovSt. Urban 15:290 min+4 min
Fri 13 NovSt. Urban 15:29+2 min+2 min
Thu 12 NovSt. Urban 15:29+1 min+2 min
Wed 11 NovSt. Urban 15:29+3 min+3 min
Tue 10 NovSt. Urban 15:29+2 min+2 min
Mon 9 NovSt. Urban 15:29+2 min+2 min
Sun 8 NovSt. Urban 15:29+1 min+1 min
Sat 7 NovSt. Urban 15:32+3 min+3 min
Fri 6 NovSt. Urban 15:29+1 min+1 min
Thu 5 NovSt. Urban 15:29+1 min—
Wed 4 NovSt. Urban 15:29+1 min+3 min
Tue 3 NovSt. Urban 15:29+1 min+1 min
Mon 2 NovSt. Urban 15:29+1 min—
Sun 1 NovSt. Urban 15:30+1 min+2 min
Sat 31 OctSt. Urban 15:30+1 min+3 min
Fri 30 OctSt. Urban 15:31+2 min+3 min
Thu 29 OctSt. Urban 15:30+1 min+1 min
Wed 28 OctSt. Urban 15:300 min+1 min
Tue 27 OctSt. Urban 15:30+1 min+5 min
Mon 26 OctSt. Urban 15:31+1 min+1 min
Sun 25 OctSt. Urban 15:290 min+3 min
Sat 24 OctSt. Urban 15:31+2 min+2 min
Fri 23 OctSt. Urban 15:30+1 min+2 min
Thu 22 OctSt. Urban 15:31+2 min+2 min
Wed 21 OctSt. Urban 15:31+2 min+2 min