S 1570 Chur – Landquart

View line S

Chur 04:53 → Landquart 05:14 Mon, Tue, Wed, Thu, Fri, Sat 0 h 21 min · 8 stops RhB

It has not run yet today

Last recorded run: Thursday 19 November 0 min

Next service: today 04:53 from Chur · Fri 20 Nov

Next departure 04:53 today · Chur
On-time · 30 days
100%
25/25 runs under 3 min
RT coverage: 25 full · 0 partial · 0 no data
On-time · 90 days
100%
39/39 runs under 3 min
RT coverage: 39 full · 0 partial · 1 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: 0 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

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

  • Early 5% · 2
  • On time 95% · 37
  • 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=6
  • 100% W n=7
  • 100% T n=7
  • 100% F n=6
  • 100% S n=6
  • — S n=0

Stops and timetable

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

Last 90 days, 39 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
04:53on time on time
04:55≈ on time ≈ on time
04:57 / 04:58≈ on time ≈ on time
05:02 / 05:03≈ on time ≈ on time
05:05≈ on time ≈ on time
05:09≈ on time ≈ on time
05:11≈ on time ≈ +1 min
05:14on 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 NovLandquart 05:140 min—
Wed 18 NovLandquart 05:140 min—
Tue 17 NovLandquart 05:130 min—
Mon 16 NovLandquart 05:14+1 min—
Sat 14 NovLandquart 05:14−1 min—
Fri 13 NovLandquart 05:15+1 min—
Thu 12 NovLandquart 05:140 min—
Wed 11 NovLandquart 05:140 min—
Tue 10 NovLandquart 05:140 min—
Mon 9 NovLandquart 05:140 min—
Sat 7 NovLandquart 05:14−1 min—
Fri 6 NovLandquart 05:140 min—
Thu 5 NovLandquart 05:140 min—
Wed 4 NovLandquart 05:13−1 min—
Tue 3 NovLandquart 05:14−1 min+1 min
Mon 2 NovLandquart 05:14−1 min—
Sat 31 OctLandquart 05:14−1 min—
Fri 30 OctLandquart 05:16+1 min—
Thu 29 OctLandquart 05:150 min—
Wed 28 OctLandquart 05:160 min—
Tue 27 OctLandquart 05:14−1 min—
Mon 26 OctLandquart 05:150 min+1 min
Sat 24 OctLandquart 05:14−1 min—
Fri 23 OctLandquart 05:14−1 min—
Thu 22 OctLandquart 05:15−1 min—
Wed 21 OctLandquart 05:14−1 min—
Tue 20 OctLandquart 05:15+1 min—
Mon 19 OctLandquart 05:16+1 min—
Sat 17 OctLandquart 05:15−1 min—
Fri 16 OctLandquart 05:130 min—