IR38 2168 St. Moritz – Preda

View line IR38

St. Moritz 19:05 → Preda 19:27 Daily 0 h 22 min · 5 stops RhB

It has not run yet today

Last recorded run: Thursday 12 November 0 min

Next service: today 19:05 from St. Moritz · Fri 13 Nov

Next departure 19:05 today · St. Moritz
On-time · 30 days
96%
24/25 runs under 3 min
RT coverage: 25 full · 0 partial · 4 no data
On-time · 90 days
96%
44/46 runs under 3 min
RT coverage: 46 full · 0 partial · 7 no data
Typical delay
0min
Median at arrival, 90 days
30 days: 0 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Preda, in minutes. One bar per run.

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

Worst days

  • Wed 21 Oct Max en route +8 min · last fix heading to Bern +8 min
  • Sat 10 Oct Max en route +4 min · last fix heading to Chur +4 min

Distribution · 90 days

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

  • Early 20% · 9
  • On time 76% · 35
  • 3–10 min 4% · 2
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=4
  • 100% T n=8
  • 89% W n=9
  • 100% T n=6
  • 100% F n=6
  • 83% S n=6
  • 100% S n=7

Stops and timetable

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

Last 90 days, 46 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:05on time on time
19:08≈ on time ≈ on time
19:12 / 19:14≈ on time ≈ +1 min
19:20≈ on time ≈ +2 min
19:27on time +2 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 12 NovPreda 19:280 min—
Wed 11 NovPreda 19:240 min—
Tue 10 NovPreda 19:240 min—
Mon 9 NovPreda 19:24−1 min+2 min
Sun 8 NovPreda 19:240 min+1 min
Sat 7 NovPreda 19:24−1 min—
Fri 6 NovPreda 19:27−1 min—
Thu 5 NovPreda 19:240 min—
Wed 4 NovPreda 19:240 min—
Tue 3 NovPreda 19:24−1 min—
Mon 2 NovPreda 19:27−2 min—
Sun 1 NovPreda 19:27−1 min—
Sat 31 OctPreda 19:28+1 min—
Fri 30 OctPreda 19:26−2 min—
Thu 29 OctPreda 19:25−3 min+2 min
Wed 28 OctBern 12:26+1 min—
Tue 27 OctBern 12:24−1 min—
Mon 26 OctBern 12:26No data—
Sun 25 OctOlten 11:560 min—
Sat 24 OctOlten 11:560 min—
Fri 23 OctBern 12:240 min—
Thu 22 OctBern 12:25No data—
Wed 21 OctBern 12:33+8 min+8 min
Tue 20 OctBern 12:25−1 min—
Mon 19 OctBern 12:25No data—
Sun 18 OctBern 12:27+2 min+2 min
Sat 17 OctBern 12:24−1 min—
Fri 16 OctBern 12:25−1 min—
Thu 15 OctBern 12:25No data—
Wed 14 OctBern 12:24−1 min—