R44 617 Andermatt → Realp

View line R44

Andermatt 05:37 → Realp 05:50 Daily 0 h 13 min · 3 stops MGB

R44 617 Andermatt–Realp: final delay under 3 min on 28 of its 29 runs with data in the last 30 days (97%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 15:06 (GMT+1).

✓ Today’s run finished

Today it reached Realp at 05:50 0 min

  1. Andermatt05:37
  2. Hospental05:41
  3. Realp05:50

Next service: tomorrow 05:37 from Andermatt · Sun 22 Nov

Next departure 05:37 tomorrow · Andermatt
On-time · 30 days
97%
28/29 runs under 3 min
RT coverage: 29 full · 0 partial · 1 no data
On-time · 90 days
96%
50/52 runs under 3 min
RT coverage: 52 full · 0 partial · 2 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Realp, 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 6 Oct Max en route +13 min · last fix heading to Brig +13 min
  • Fri 13 Nov Max en route +12 min · last fix heading to Brig +6 min

Distribution · 90 days

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

  • Early 8% · 4
  • On time 88% · 46
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 52 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
05:37on time on time
05:41≈ on time ≈ +1 min
05:50on time +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
Sat 21 NovRealp 05:490 min—
Fri 20 NovBrig 12:43+1 min—
Thu 19 NovBrig 12:42No data—
Wed 18 NovBrig 12:420 min—
Tue 17 NovBrig 12:420 min—
Mon 16 NovBrig 12:420 min—
Sun 15 NovRealp 05:490 min—
Sat 14 NovRealp 05:490 min—
Fri 13 NovBrig 12:48+6 min+12 min
Thu 12 NovBrig 12:420 min—
Wed 11 NovBrig 12:43+1 min+2 min
Tue 10 NovBrig 12:44+2 min+2 min
Mon 9 NovBrig 12:420 min—
Sun 8 NovRealp 05:490 min—
Sat 7 NovRealp 05:490 min—
Fri 6 NovBrig 12:390 min—
Thu 5 NovBrig 12:420 min—
Wed 4 NovBrig 12:390 min—
Tue 3 NovBrig 12:420 min—
Mon 2 NovBrig 12:420 min—
Sun 1 NovRealp 05:490 min—
Sat 31 OctRealp 05:50−1 min—
Fri 30 OctBrig 12:420 min—
Thu 29 OctBrig 12:420 min—
Wed 28 OctBrig 12:45+2 min+2 min
Tue 27 OctBrig 12:44+1 min+1 min
Mon 26 OctBrig 12:420 min—
Sun 25 OctRealp 05:50−1 min—
Sat 24 OctRealp 05:50−1 min—
Fri 23 OctBrig 12:420 min—