IR38 1148 St. Moritz – Chur

View line IR38

St. Moritz 14:05 → Chur 16:02 Daily 1 h 57 min · 10 stops RhB

Running now · updated 15:02

Position estimated from the timetable

Between Filisur and Tiefencastel −1 min

Estimated arrival at Chur 16:02 · 41 km/h

  1. St. Moritz14:05
  2. Samedan14:12
  3. Preda14:28
  4. Filisur14:59
  5. Tiefencastel15:14
  6. Reichenau-Tamins15:52
  7. Chur16:02

Today it is running no worse than usual: typical arrival delay is −1 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%
47/47 runs under 3 min
RT coverage: 46 full · 1 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
0min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

Arrival delay at Chur, 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

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

  • Early 23% · 11
  • On time 77% · 36
  • 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=6
  • 100% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 47 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
14:05on time on timePassed
14:08≈ on time ≈ on timePassed
14:12 / 14:15≈ on time ≈ on timePassed
14:28 / 14:29≈ on time ≈ on timePassed
14:46 / 14:47≈ on time ≈ on timePassed
14:59 / 15:00≈ on time ≈ on timePassed
15:14 / 15:15≈ on time ≈ on timeNext
15:31 / 15:33≈ on time ≈ on time
15:52≈ 1 min early ≈ on time
16:021 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 19 NovTiefencastel 14:59Partial coverage−1 min—
Wed 18 NovChur 16:02−1 min—
Tue 17 NovChur 16:030 min—
Mon 16 NovChur 16:030 min—
Sun 15 NovChur 16:020 min—
Sat 14 NovChur 16:02−1 min—
Fri 13 NovChur 16:03−1 min—
Thu 12 NovChur 16:03−1 min—
Wed 11 NovChur 16:02−1 min—
Tue 10 NovChur 16:02−1 min—
Mon 9 NovChur 16:02−1 min—
Sun 8 NovChur 16:02−2 min—
Sat 7 NovChur 16:02−1 min—
Fri 6 NovChur 16:02−1 min—
Thu 5 NovChur 16:02−1 min—
Wed 4 NovChur 16:02−1 min—
Tue 3 NovChur 16:030 min—
Mon 2 NovChur 16:02−1 min—
Sun 1 NovChur 16:030 min—
Sat 31 OctChur 16:02−1 min—
Fri 30 OctChur 16:02−1 min—
Thu 29 OctChur 16:030 min—
Wed 28 OctChur 16:02−1 min—
Tue 27 OctChur 16:03−1 min+8 min
Mon 26 OctChur 16:030 min—
Sun 25 OctChur 16:030 min—
Sat 24 OctChur 16:030 min—
Fri 23 OctChur 16:02−1 min—
Thu 22 OctChur 16:030 min—
Wed 21 OctChur 16:030 min—