IR38 2120 Samedan – Preda

View line IR38

Samedan 13:14 → Preda 13:27 Daily 0 h 13 min · 3 stops RhB

✓ Today’s run finished

Today it reached Preda at 13:27 0 min

  1. Samedan13:14
  2. Spinas13:20
  3. Preda13:27

Next service: tomorrow 13:14 from Samedan · Fri 6 Nov

Next departure 13:14 tomorrow · Samedan
On-time · 30 days
76%
13/17 runs under 3 min
RT coverage: 17 full · 0 partial · 13 no data
On-time · 90 days
81%
25/31 runs under 3 min
RT coverage: 31 full · 0 partial · 27 no data
Typical delay
+1min
Median at arrival, 90 days
30 days: +2 min
P90
+5min
9 in 10 runs arrive with less than this
30 days: +4 min

Last 30 days

Arrival delay at Preda, 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 21 Oct Max en route +6 min · last fix heading to Luzern +6 min
  • Fri 14 Aug Max en route +6 min · last fix heading to Luzern +5 min
  • Thu 29 Oct Max en route +9 min · last fix heading to Luzern +5 min
  • Thu 13 Aug Max en route +5 min · last fix heading to Luzern +5 min
  • Sun 25 Oct Max en route +4 min · last fix heading to Luzern +4 min

Distribution · 90 days

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

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

On-time by weekday

  • 100% M n=4
  • 100% T n=4
  • 75% W n=4
  • 33% T n=3
  • 50% F n=4
  • 100% S n=5
  • 86% S n=7

Stops and timetable

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

Last 90 days, 31 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
13:14on time +1 min
13:20≈ +1 min ≈ +2 min
13:27+1 min +5 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 5 NovPreda 07:240 min—
Wed 4 NovLuzern 14:28+2 min+2 min
Tue 3 NovLuzern 14:28+2 min+2 min
Mon 2 NovLuzern 14:24−2 min—
Sun 1 NovLuzern 14:27+1 min+1 min
Sat 31 OctLuzern 14:27+1 min+1 min
Fri 30 OctLuzern 14:29+3 min+3 min
Thu 29 OctLuzern 14:26+5 min+9 min
Wed 28 OctLuzern 14:28+2 min+2 min
Tue 27 OctLuzern 14:260 min—
Mon 26 OctLuzern 14:26No data—
Sun 25 OctLuzern 14:29+4 min+4 min
Sat 24 OctLuzern 14:26+1 min—
Fri 23 OctLuzern 14:29+3 min+3 min
Thu 22 OctLuzern 14:26No data—
Wed 21 OctLuzern 14:32+6 min+6 min
Tue 20 OctLuzern 14:29+2 min+2 min
Mon 19 OctLuzern 14:26No data—
Sun 18 OctLuzern 14:26No data—
Sat 17 OctLuzern 14:26No data—
Fri 16 OctLuzern 14:27No data—
Thu 15 OctLuzern 14:26No data—
Wed 14 OctLuzern 14:26No data—
Tue 13 OctLuzern 14:26No data—
Mon 12 OctLuzern 14:26No data—
Sun 11 OctLuzern 14:260 min+2 min
Sat 10 OctLuzern 14:26−1 min—
Fri 9 OctLuzern 14:26No data—
Thu 8 OctLuzern 14:26No data—
Wed 7 OctLuzern 14:26No data—