R4 1279 Klosters Platz – Susch

View line R4

Klosters Platz 22:34 → Susch 22:53 Mon, Tue, Wed, Thu, Sun 0 h 19 min · 2 stops RhB

It does not run today

Last recorded run: Thursday 12 November −2 min

Next service: Sunday 22:34 from Klosters Platz · Sun 15 Nov

Next departure 22:34 Sunday · Klosters Platz
On-time · 30 days
100%
21/21 runs under 3 min
RT coverage: 21 full · 0 partial · 0 no data
On-time · 90 days
96%
48/50 runs under 3 min
RT coverage: 50 full · 0 partial · 1 no data
Typical delay
−3min
Median at arrival, 90 days
30 days: −3 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Susch, 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 29 Sept Max en route +13 min · last fix heading to Susch +12 min
  • Sun 13 Sept Max en route +7 min · last fix heading to Susch +7 min

Distribution · 90 days

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

  • Early 66% · 33
  • On time 30% · 15
  • 3–10 min 2% · 1
  • 10–30 min 2% · 1
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=12
  • 90% T n=10
  • 100% W n=10
  • 100% T n=10
  • — F n=0
  • — S n=0
  • 88% S n=8

Stops and timetable

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

Last 90 days, 50 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
22:34on time on time
22:533 min early on time

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 12 NovSusch 22:52−2 min—
Wed 11 NovSusch 22:54+2 min+3 min
Tue 10 NovSusch 22:49−3 min—
Mon 9 NovSusch 22:52−3 min—
Sun 8 NovSusch 22:530 min—
Thu 5 NovSusch 22:48−3 min—
Wed 4 NovSusch 22:49−2 min—
Tue 3 NovSusch 22:49−3 min—
Mon 2 NovSusch 22:49−3 min—
Sun 1 NovSusch 22:49−3 min—
Thu 29 OctSusch 22:53−1 min—
Wed 28 OctSusch 22:53−1 min—
Tue 27 OctSusch 22:51−3 min—
Mon 26 OctSusch 22:51−3 min—
Sun 25 OctSusch 22:54+1 min—
Thu 22 OctSusch 22:540 min—
Wed 21 OctSusch 22:50−3 min—
Tue 20 OctSusch 22:51−4 min—
Mon 19 OctSusch 22:530 min—
Sun 18 OctSusch 22:51−3 min—
Thu 15 OctSusch 22:51−3 min—
Wed 14 OctSusch 22:51−4 min—
Tue 13 OctSusch 22:51−3 min—
Mon 12 OctSusch 22:50−3 min—
Sun 11 OctSusch 22:51−3 min—
Thu 8 OctSusch 22:51−3 min—
Wed 7 OctSusch 22:51−3 min—
Tue 6 OctSusch 22:51−3 min—
Mon 5 OctSusch 22:51−3 min—
Sun 4 OctSusch 22:50−3 min—