RE13 1062 Klosters Platz → Landquart

View line RE13

Klosters Platz 19:00 → Landquart 19:39 Daily 0 h 39 min · 5 stops RhB

RE13 1062 Klosters Platz–Landquart: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. TrainsRadar data as of 21 Nov 2026, 20:04 (GMT+1).

✓ Today’s run finished

Today it reached Landquart at 19:39 −1 min

  1. Klosters Platz19:00
  2. Saas im Prättigau19:11
  3. Küblis19:17
  4. Schiers19:28
  5. Landquart19:39

Next service: tomorrow 19:00 from Klosters Platz · Sun 22 Nov

Next departure 19:00 tomorrow · Klosters Platz
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
100%
49/49 runs under 3 min
RT coverage: 49 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 Landquart, in minutes. One bar per run.

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

Distribution · 90 days

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

  • Early 0% · 0
  • On time 100% · 49
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=7
  • 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 (5 stops).

Last 90 days, 49 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
19:00on time on time
19:11≈ on time ≈ on time
19:17 / 19:18≈ on time ≈ on time
19:28 / 19:29≈ on time ≈ +1 min
19:39on 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 19:39−1 min—
Fri 20 NovLandquart 19:390 min—
Thu 19 NovLandquart 19:390 min+2 min
Wed 18 NovLandquart 19:39+1 min+2 min
Tue 17 NovLandquart 19:39−1 min—
Mon 16 NovLandquart 19:390 min+2 min
Sun 15 NovLandquart 19:390 min—
Sat 14 NovLandquart 19:390 min—
Fri 13 NovLandquart 19:39−1 min—
Thu 12 NovLandquart 19:390 min—
Wed 11 NovLandquart 19:390 min—
Tue 10 NovLandquart 19:390 min+1 min
Mon 9 NovLandquart 19:39−1 min—
Sun 8 NovLandquart 19:390 min—
Sat 7 NovLandquart 19:390 min—
Fri 6 NovLandquart 19:390 min—
Thu 5 NovLandquart 19:390 min—
Wed 4 NovLandquart 19:39−1 min—
Tue 3 NovLandquart 19:39−1 min+2 min
Mon 2 NovLandquart 19:43+2 min+3 min
Sun 1 NovLandquart 19:39−1 min—
Sat 31 OctLandquart 19:39−1 min—
Fri 30 OctLandquart 19:400 min—
Thu 29 OctLandquart 19:41+1 min+2 min
Wed 28 OctLandquart 19:43+3 min+3 min
Tue 27 OctLandquart 19:400 min—
Mon 26 OctLandquart 19:40−1 min—
Sun 25 OctLandquart 19:390 min—
Sat 24 OctLandquart 19:390 min—
Fri 23 OctLandquart 19:39−1 min—