RE38 2176 St. Moritz – Preda

View line RE38

St. Moritz 21:02 → Preda 21:27 Fri, Sat 0 h 25 min · 6 stops RhB

✓ Today’s run finished

Today it reached Preda at 21:27 0 min

  1. St. Moritz21:02
  2. Celerina21:05
  3. Samedan21:10
  4. Bever21:15
  5. Spinas21:20
  6. Preda21:27
On-time · 30 days
90%
27/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
92%
57/62 runs under 3 min
RT coverage: 62 full · 0 partial · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+3min
9 in 10 runs arrive with less than this
30 days: +3 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 +5 min · last fix heading to Trogen +5 min
  • Thu 29 Oct Max en route +5 min · last fix heading to Trogen +5 min
  • Tue 27 Oct Max en route +5 min · last fix heading to Trogen +5 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Trogen +4 min
  • Tue 15 Sept Max en route +3 min · last fix heading to Gfeld +3 min

Distribution · 90 days

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

  • Early 19% · 12
  • On time 73% · 45
  • 3–10 min 8% · 5
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=9
  • 80% T n=10
  • 88% W n=8
  • 75% T n=8
  • 100% F n=9
  • 100% S n=9
  • 100% S n=9

Stops and timetable

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

Last 90 days, 62 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
21:02on time on time
21:05 / 21:06≈ on time ≈ on time
21:10 / 21:13≈ on time ≈ +1 min
21:15≈ on time ≈ +1 min
21:20≈ on time ≈ +2 min
21:27on time +3 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 13 NovPreda 21:240 min—
Thu 12 NovTrogen 18:54+3 min+3 min
Wed 11 NovTrogen 18:530 min+1 min
Tue 10 NovTrogen 18:530 min—
Mon 9 NovTrogen 18:53+1 min—
Sun 8 NovTrogen 18:54+1 min+2 min
Sat 7 NovPreda 21:24−3 min+1 min
Fri 6 NovPreda 21:240 min+2 min
Thu 5 NovTrogen 18:54+3 min+3 min
Wed 4 NovTrogen 18:54+1 min+1 min
Tue 3 NovTrogen 18:54+3 min+3 min
Mon 2 NovTrogen 18:54+1 min+1 min
Sun 1 NovTrogen 18:53−1 min—
Sat 31 OctPreda 21:26−2 min+2 min
Fri 30 OctPreda 21:25−3 min+4 min
Thu 29 OctTrogen 18:58+5 min+5 min
Wed 28 OctTrogen 18:55+2 min+4 min
Tue 27 OctTrogen 18:58+5 min+5 min
Mon 26 OctTrogen 18:54+1 min+1 min
Sun 25 OctTrogen 18:53+1 min+1 min
Sat 24 OctTrogen 18:530 min+2 min
Fri 23 OctTrogen 18:530 min—
Thu 22 OctTrogen 18:530 min—
Wed 21 OctTrogen 18:58+5 min+5 min
Tue 20 OctTrogen 18:52−1 min—
Mon 19 OctTrogen 18:55+2 min+2 min
Sun 18 OctTrogen 18:54+1 min—
Sat 17 OctTrogen 18:56+3 min+3 min
Fri 16 OctTrogen 18:540 min—
Thu 15 OctTrogen 18:54+1 min+1 min