R43 557 Andermatt → Visp

View line R43

Andermatt 15:37 → Visp 17:50 Daily 2 h 13 min · 24 stops MGB

R43 557 Andermatt–Visp: final delay under 3 min on 28 of its 29 runs with data in the last 30 days (97%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 03:27 (GMT+1).

It has not run yet today

Last recorded run: Saturday 21 November −1 min

Next service: today 15:37 from Andermatt · Sun 22 Nov

Next departure 15:37 today · Andermatt
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 0 no data
On-time · 90 days
96%
51/53 runs under 3 min
RT coverage: 53 full · 0 partial · 1 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 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

  • Wed 18 Nov Max en route +38 min · last fix heading to Visp +38 min
  • Wed 14 Oct Max en route +5 min · last fix heading to Chur +5 min

Distribution · 90 days

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

  • Early 49% · 26
  • On time 47% · 25
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 2% · 1

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 71% W n=7
  • 100% T n=8
  • 100% F n=7
  • 100% S n=9
  • 100% S n=8

Stops and timetable

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

Last 90 days, 53 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
15:37on time on time
15:41≈ on time ≈ on time
15:49 / 15:50≈ on time ≈ on time
16:09 / 16:12≈ on time ≈ on time
16:15≈ on time ≈ on time
16:18≈ on time ≈ on time
16:21≈ on time ≈ on time
16:24 / 16:25≈ on time ≈ on time
16:29≈ on time ≈ +1 min
16:31≈ on time ≈ +1 min
16:34≈ on time ≈ +1 min
16:37≈ on time ≈ +1 min
16:40≈ on time ≈ +1 min
16:45≈ 1 min early ≈ +1 min
16:53 / 16:55≈ 1 min early ≈ +1 min
16:57≈ 1 min early ≈ +1 min
17:01≈ 1 min early ≈ +1 min
17:09 / 17:10≈ 1 min early ≈ +1 min
17:14 / 17:15≈ 1 min early ≈ +1 min
17:21 / 17:22≈ 1 min early ≈ +1 min
17:27 / 17:28≈ 1 min early ≈ +1 min
17:33 / 17:38≈ 1 min early ≈ +1 min
17:45≈ 1 min early ≈ +1 min
17:501 min early +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 NovVisp 17:49−1 min—
Fri 20 NovVisp 17:490 min—
Thu 19 NovVisp 17:49−1 min+2 min
Wed 18 NovVisp 17:49+38 min+38 min
Tue 17 NovVisp 17:49−1 min—
Mon 16 NovVisp 17:49−1 min+2 min
Sun 15 NovVisp 17:49−2 min—
Sat 14 NovVisp 17:49−2 min—
Fri 13 NovVisp 17:49−1 min—
Thu 12 NovVisp 17:49−2 min—
Wed 11 NovVisp 17:52+1 min—
Tue 10 NovVisp 17:48−3 min—
Mon 9 NovVisp 17:49−2 min—
Sun 8 NovChur 07:53−1 min—
Sat 7 NovChur 07:49−2 min—
Fri 6 NovChur 07:53−1 min—
Thu 5 NovChur 07:52−1 min—
Wed 4 NovChur 07:52−1 min—
Tue 3 NovChur 07:52−1 min—
Mon 2 NovChur 07:530 min—
Sun 1 NovChur 07:530 min—
Sat 31 OctChur 07:52−1 min—
Fri 30 OctChur 07:530 min—
Thu 29 OctChur 07:52−1 min—
Wed 28 OctChur 07:52−2 min—
Tue 27 OctChur 07:53−1 min—
Mon 26 OctChur 07:56+3 min+3 min
Sun 25 OctChur 07:52−1 min—
Sat 24 OctChur 07:530 min—
Fri 23 OctChur 07:52−1 min—