R40 59 Täsch → Zermatt

View line R40

Täsch 11:15 → Zermatt 11:27 Daily 0 h 12 min · 2 stops MGB

R40 59 Täsch–Zermatt: final delay under 3 min on 21 of its 21 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 16:23 (GMT+1).

✓ Today’s run finished

Today it reached Zermatt at 11:27 0 min

  1. Täsch11:15
  2. Zermatt11:27

Next service: tomorrow 11:15 from Täsch · Sun 22 Nov

Next departure 11:15 tomorrow · Täsch
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 3 no data
On-time · 90 days
100%
34/34 runs under 3 min
RT coverage: 34 full · 0 partial · 6 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 Zermatt, 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

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

  • Early 3% · 1
  • On time 97% · 33
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 34 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
11:15on time on time
11:27on 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
Sat 21 NovZermatt 11:280 min—
Fri 20 NovSte-Croix 18:370 min—
Thu 19 NovSte-Croix 18:370 min—
Wed 18 NovSte-Croix 18:37No data—
Tue 17 NovSte-Croix 18:380 min—
Mon 16 NovSte-Croix 18:38+1 min+1 min
Sun 15 NovZermatt 11:27−1 min—
Sat 14 NovZermatt 11:27−1 min—
Fri 13 NovSte-Croix 18:37−1 min—
Thu 12 NovSte-Croix 18:370 min—
Wed 11 NovSte-Croix 18:370 min+2 min
Tue 10 NovSte-Croix 18:370 min—
Mon 9 NovSte-Croix 18:37No data—
Fri 6 NovSte-Croix 18:38+1 min+1 min
Thu 5 NovSte-Croix 18:370 min—
Wed 4 NovSte-Croix 18:370 min—
Tue 3 NovSte-Croix 18:38+1 min+1 min
Mon 2 NovSte-Croix 18:370 min—
Fri 30 OctSte-Croix 18:38+1 min+1 min
Thu 29 OctSte-Croix 18:370 min—
Wed 28 OctSte-Croix 18:370 min—
Tue 27 OctSte-Croix 18:370 min—
Mon 26 OctSte-Croix 18:37No data—
Fri 23 OctSte-Croix 18:370 min—
Thu 22 OctSte-Croix 18:370 min—
Wed 21 OctSte-Croix 18:370 min—
Mon 19 OctSte-Croix 18:37No data—
Fri 16 OctSte-Croix 18:37No data—
Thu 15 OctSte-Croix 18:370 min—
Wed 14 OctSte-Croix 18:370 min—