R42 30359 Fiesch – Visp

View line R42

Fiesch 17:29 → Visp 18:33 Daily 1 h 04 min · 10 stops MGB

✓ Today’s run finished

Today it reached Visp at 18:33 0 min

  1. Fiesch17:29
  2. Lax17:34
  3. Grengiols17:42
  4. Mörel17:53
  5. Bitsch18:01
  6. Eyholz18:29
  7. Visp18:33

Next service: tomorrow 17:29 from Fiesch · Sat 7 Nov

Next departure 17:29 tomorrow · Fiesch
On-time · 30 days
96%
25/26 runs under 3 min
RT coverage: 26 full · 0 partial · 2 no data
On-time · 90 days
97%
29/30 runs under 3 min
RT coverage: 30 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 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

  • Thu 15 Oct Max en route +4 min · last fix heading to Visp +4 min

Distribution · 90 days

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

  • Early 20% · 6
  • On time 77% · 23
  • 3–10 min 3% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 100% W n=4
  • 75% T n=4
  • 100% F n=6
  • 100% S n=4
  • 100% S n=4

Stops and timetable

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

Last 90 days, 30 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:29on time on time
17:31≈ on time ≈ on time
17:34≈ on time ≈ on time
17:42 / 17:43≈ on time ≈ on time
17:47≈ on time ≈ on time
17:53 / 17:57≈ on time ≈ on time
18:01≈ on time ≈ +1 min
18:06 / 18:22≈ on time ≈ +1 min
18:29≈ on time ≈ +1 min
18:33on 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 NovVisp 18:340 min—
Thu 5 NovVisp 18:340 min—
Wed 4 NovVisp 18:33−1 min—
Tue 3 NovVisp 18:340 min—
Mon 2 NovVisp 18:340 min—
Sun 1 NovVisp 18:340 min—
Sat 31 OctVisp 18:33−1 min—
Fri 30 OctVisp 18:340 min—
Thu 29 OctVisp 18:340 min—
Wed 28 OctVisp 18:350 min—
Tue 27 OctVisp 18:340 min—
Mon 26 OctVisp 18:350 min—
Sun 25 OctVisp 18:33−1 min—
Sat 24 OctVisp 18:340 min—
Fri 23 OctVisp 18:340 min—
Thu 22 OctVisp 18:33−1 min—
Wed 21 OctVisp 18:35+1 min+1 min
Tue 20 OctVisp 18:340 min—
Mon 19 OctVisp 18:340 min—
Sun 18 OctVisp 18:33−1 min—
Sat 17 OctVisp 18:33−1 min—
Fri 16 OctVisp 18:37+3 min+3 min
Thu 15 OctVisp 18:38+4 min+4 min
Wed 14 OctVisp 18:35+1 min+1 min
Tue 13 OctVisp 18:350 min—
Mon 12 OctVisp 18:33−1 min—
Sun 11 OctOlten 07:25No data—
Sat 10 OctOlten 07:26No data—
Fri 18 SeptBern 00:270 min—
Sun 13 SeptBern 00:27−2 min—