R24 1012 Klosters Platz → Landquart

View line R24

Klosters Platz 06:29 → Landquart 07:13 Daily 0 h 44 min · 12 stops RhB

✓ Today’s run finished

Today it reached Landquart at 07:13 −1 min

  1. Klosters Platz06:29
  2. Saas im Prättigau06:40
  3. Fideris06:50
  4. Furna06:54
  5. Schiers06:59
  6. Seewis-Pardisla07:05
  7. Landquart07:13

Next service: tomorrow 06:29 from Klosters Platz · Sun 22 Nov

Next departure 06:29 tomorrow · Klosters Platz
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 · 1 no data
Typical delay
0min
Median at arrival, 90 days
30 days: +1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: +2 min

Last 30 days

Arrival delay at Landquart, 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 10 Nov Max en route +4 min · last fix heading to Landquart +4 min

Distribution · 90 days

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

  • Early 2% · 1
  • On time 96% · 46
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

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

Stops and timetable

Timetable of the latest run from the operator’s GTFS (12 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
06:29on time on time
06:32≈ on time ≈ on time
06:40≈ on time ≈ on time
06:45 / 06:46≈ on time ≈ on time
06:50≈ on time ≈ +1 min
06:52≈ on time ≈ +1 min
06:54≈ on time ≈ +1 min
06:59 / 07:00≈ on time ≈ +1 min
07:03≈ on time ≈ +1 min
07:05≈ on time ≈ +1 min
07:09≈ on time ≈ +1 min
07:13on 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
Sat 21 NovLandquart 07:13−1 min—
Fri 20 NovLandquart 07:14+1 min+1 min
Thu 19 NovLandquart 07:14+1 min—
Wed 18 NovLandquart 07:140 min—
Tue 17 NovLandquart 07:130 min—
Mon 16 NovLandquart 07:14+1 min—
Sun 15 NovLandquart 07:140 min—
Sat 14 NovLandquart 07:140 min—
Fri 13 NovLandquart 07:17+2 min+2 min
Thu 12 NovLandquart 07:15+2 min+2 min
Wed 11 NovLandquart 07:17+3 min+3 min
Tue 10 NovLandquart 07:18+4 min+4 min
Mon 9 NovLandquart 07:140 min—
Sun 8 NovLandquart 07:14−1 min—
Sat 7 NovLandquart 07:140 min—
Fri 6 NovLandquart 07:140 min—
Thu 5 NovLandquart 07:14+1 min—
Wed 4 NovLandquart 07:14+1 min—
Tue 3 NovLandquart 07:14+1 min—
Mon 2 NovLandquart 07:14+1 min—
Sun 1 NovLandquart 07:13−1 min—
Sat 31 OctLandquart 07:140 min—
Fri 30 OctLandquart 07:140 min—
Thu 29 OctLandquart 07:15+1 min+1 min
Wed 28 OctLandquart 07:15+1 min—
Tue 27 OctLandquart 07:16+1 min+1 min
Mon 26 OctLandquart 07:15+1 min—
Sun 25 OctLandquart 07:130 min—
Sat 24 OctLandquart 07:13−1 min—
Fri 23 OctLandquart 07:15+1 min+1 min