S1 1563 Schiers → Thusis

View line S1

Schiers 19:02 → Thusis 20:19 Daily 1 h 17 min · 21 stops RhB

S1 1563 Schiers–Thusis: final delay under 3 min on 30 of its 30 runs with data in the last 30 days (100%). Median final delay: 0 min. Running now, on time. Expected at Thusis: 20:19. TrainsRadar data as of 22 Nov 2026, 19:22 (GMT+1).

Running now · updated 19:22

Position estimated from the timetable

Between Igis and Zizers 0 min

Estimated arrival at Thusis 20:19 · 26 km/h

  1. Schiers19:02
  2. Landquart19:14
  3. Igis19:22
  4. Zizers19:24
  5. Untervaz-Trimmis19:27
  6. Chur West19:40
  7. Thusis20:19

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

On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 29 full · 1 partial · 0 no data
On-time · 90 days
100%
50/50 runs under 3 min
RT coverage: 49 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 Thusis, 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

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

  • Early 0% · 0
  • On time 100% · 50
  • 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=8

Stops and timetable

Timetable of the latest run from the operator’s GTFS (21 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 10Today
19:02on time on timePassed
19:06≈ on time ≈ on timePassed
19:11≈ on time ≈ on timePassed
19:14 / 19:18≈ on time ≈ on timePassed
19:20≈ on time ≈ on timePassed
19:22≈ on time ≈ on timePassed
19:24≈ on time ≈ on timeNext
19:27 / 19:28≈ on time ≈ on time
19:33≈ on time ≈ on time
19:36 / 19:38≈ on time ≈ on time
19:40≈ on time ≈ on time
19:43≈ on time ≈ +1 min
19:46≈ on time ≈ +1 min
19:48≈ on time ≈ +1 min
19:51≈ on time ≈ +1 min
19:56≈ on time ≈ +1 min
19:58 / 20:01≈ on time ≈ +1 min
20:06 / 20:09≈ on time ≈ +1 min
20:12≈ on time ≈ +1 min
20:15≈ on time ≈ +1 min
20:19on 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
Sun 22 NovLandquart Ried 19:19Partial coverage+1 min—
Sat 21 NovThusis 20:19−1 min+1 min
Fri 20 NovThusis 20:190 min—
Thu 19 NovThusis 20:190 min—
Wed 18 NovThusis 20:19+1 min—
Tue 17 NovThusis 20:190 min+1 min
Mon 16 NovThusis 20:19−1 min—
Sun 15 NovThusis 20:190 min—
Sat 14 NovThusis 20:180 min—
Fri 13 NovThusis 20:190 min—
Thu 12 NovThusis 20:200 min+2 min
Wed 11 NovThusis 20:19−1 min—
Tue 10 NovThusis 20:19+1 min+2 min
Mon 9 NovThusis 20:19+1 min—
Sun 8 NovThusis 20:190 min—
Sat 7 NovThusis 20:190 min—
Fri 6 NovThusis 20:190 min+1 min
Thu 5 NovThusis 20:18−1 min—
Wed 4 NovThusis 20:190 min—
Tue 3 NovThusis 20:19−1 min+1 min
Mon 2 NovThusis 20:22+2 min+3 min
Sun 1 NovThusis 20:190 min+1 min
Sat 31 OctThusis 20:200 min+1 min
Fri 30 OctThusis 20:200 min—
Thu 29 OctThusis 20:200 min—
Wed 28 OctThusis 20:21+1 min+1 min
Tue 27 OctThusis 20:21+1 min—
Mon 26 OctThusis 20:20−1 min+2 min
Sun 25 OctThusis 20:200 min—
Sat 24 OctThusis 20:200 min—