R38 4366 St. Moritz – Samedan

View line R38

St. Moritz 18:19 → Samedan 18:26 Daily 0 h 07 min · 3 stops RhB

✓ Today’s run finished

Today it reached Samedan at 18:26 0 min

  1. St. Moritz18:19
  2. Celerina18:22
  3. Samedan18:26

Next service: tomorrow 18:19 from St. Moritz · Mon 16 Nov

Next departure 18:19 tomorrow · St. Moritz
On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
47/48 runs under 3 min
RT coverage: 48 full · 0 partial · 0 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 Samedan, in minutes. One bar per run.

  • On time (<3 min)
  • 3–10 min
  • 10–30 min
  • 30+ min
  • Partial coverage
  • No data

Worst days

  • Mon 2 Nov Max en route +5 min · last fix heading to Samedan +5 min

Distribution · 90 days

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

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

On-time by weekday

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

Stops and timetable

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

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