RE3 1350 St. Moritz – Klosters Platz

View line RE3

St. Moritz 14:47 → Klosters Platz 15:56 Daily 1 h 09 min · 7 stops RhB

Running now · updated 15:10

Position estimated from the timetable

Between Samedan and Zuoz 0 min

Estimated arrival at Klosters Platz 15:56 · 32 km/h

  1. St. Moritz14:47
  2. Celerina14:50
  3. Samedan14:55
  4. Zuoz15:09
  5. S-chanf15:14
  6. Zernez15:29
  7. Klosters Platz15:56

Today it is running no worse than usual: typical arrival delay is 0 min; 97% of the last 30 runs arrived on time.

On-time · 30 days
97%
29/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
96%
45/47 runs under 3 min
RT coverage: 46 full · 1 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 Klosters Platz, in minutes. One bar per run.

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

Worst days

  • Thu 8 Oct Max en route +6 min · last fix heading to Vevey +6 min
  • Tue 10 Nov Max en route +4 min · last fix heading to Vevey +4 min

Distribution · 90 days

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

  • Early 26% · 12
  • On time 70% · 33
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

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

Last 90 days, 47 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 10Today
14:47on time +1 minPassed
14:50 / 14:51≈ on time ≈ on timePassed
14:55 / 14:58≈ on time ≈ +1 minPassed
15:09 / 15:11≈ on time ≈ +1 minNext
15:14≈ on time ≈ +1 min
15:29 / 15:31≈ on time ≈ +1 min
15:56on 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
Thu 19 NovZuoz 15:09Partial coverage0 min+1 min
Wed 18 NovVevey 17:540 min+2 min
Tue 17 NovVevey 17:54+1 min—
Mon 16 NovVevey 17:540 min+2 min
Sun 15 NovVevey 17:54−3 min—
Sat 14 NovVevey 17:54−1 min+3 min
Fri 13 NovVevey 17:54+1 min—
Thu 12 NovVevey 17:540 min—
Wed 11 NovVevey 17:54−3 min—
Tue 10 NovVevey 17:54+4 min+4 min
Mon 9 NovVevey 17:540 min—
Sun 8 NovVevey 17:54−1 min—
Sat 7 NovVevey 17:54−1 min—
Fri 6 NovVevey 17:54+1 min+1 min
Thu 5 NovVevey 17:540 min+3 min
Wed 4 NovVevey 17:54+1 min+1 min
Tue 3 NovVevey 17:54+1 min+1 min
Mon 2 NovVevey 17:54+2 min+2 min
Sun 1 NovVevey 17:560 min—
Sat 31 OctVevey 17:56−3 min—
Fri 30 OctVevey 17:56−1 min—
Thu 29 OctVevey 17:560 min+2 min
Wed 28 OctVevey 17:54−2 min+2 min
Tue 27 OctVevey 17:540 min+2 min
Mon 26 OctVevey 17:55−2 min+1 min
Sun 25 OctVevey 17:54+1 min+3 min
Sat 24 OctVevey 17:55−1 min+2 min
Fri 23 OctVevey 17:58+2 min+3 min
Thu 22 OctVevey 17:56−1 min+3 min
Wed 21 OctVevey 17:560 min+2 min