R30 2235 Château-d'Oex → Montreux

View line R30

Château-d'Oex 21:04 → Montreux 22:18 Daily 1 h 14 min · 21 stops MOB

R30 2235 Château-d'Oex–Montreux: final delay under 3 min on 17 of its 17 runs with data in the last 30 days (100%). Median final delay: −1 min. TrainsRadar data as of 22 Nov 2026, 22:16 (GMT+1).

Running now · updated 22:16

Position estimated from the timetable

Between Montreux-Collège and Montreux No data

Estimated arrival at Montreux 22:18 · 8 km/h

  1. Château-d'Oex21:04
  2. La Tine21:14
  3. Les Cases21:38
  4. Sendy-Sollard21:50
  5. Chernex22:07
  6. Montreux-Collège22:14
  7. Montreux22:18
On-time · 30 days
100%
17/17 runs under 3 min
RT coverage: 17 full · 0 partial · 13 no data
On-time · 90 days
100%
45/45 runs under 3 min
RT coverage: 45 full · 0 partial · 27 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+1min
9 in 10 runs arrive with less than this
30 days: 0 min

Last 30 days

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

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

  • Early 31% · 14
  • On time 69% · 31
  • 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=8
  • 100% W n=6
  • 100% T n=7
  • 100% F n=5
  • 100% S n=5
  • 100% S n=7

Stops and timetable

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

Last 90 days, 45 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
21:04on time on timePassed
21:08≈ on time ≈ on timePassed
21:09≈ on time ≈ on timePassed
21:14≈ on time ≈ on timePassed
21:21 / 21:23≈ on time ≈ +1 minPassed
21:28≈ on time ≈ on timePassed
21:34≈ on time ≈ +1 minPassed
21:38≈ on time ≈ on timePassed
21:41≈ on time ≈ +1 minPassed
21:47≈ on time ≈ +1 minPassed
21:50≈ on time ≈ +1 minPassed
21:56 / 22:00≈ on time ≈ +1 minPassed
22:03≈ 1 min early ≈ +1 minPassed
22:07≈ 1 min early ≈ +1 minPassed
22:09≈ 1 min early ≈ +1 minPassed
22:10≈ 1 min early ≈ +1 minPassed
22:11≈ 1 min early ≈ +1 minPassed
22:12≈ 1 min early ≈ +1 minPassed
22:13≈ 1 min early ≈ +1 minPassed
22:14≈ 1 min early ≈ +1 minPassed
22:181 min early +1 minNext

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 NovMontreux 22:140 min—
Sat 21 NovAppenzell 00:380 min—
Fri 20 NovAppenzell 00:380 min—
Thu 19 NovSpeicher 23:29−1 min—
Wed 18 NovSpeicher 23:29−1 min—
Tue 17 NovSpeicher 23:29−1 min—
Mon 16 NovSpeicher 23:290 min—
Sun 15 NovSpeicher 23:29−1 min—
Sat 14 NovAppenzell 00:37−1 min—
Fri 13 NovAppenzell 00:390 min—
Thu 12 NovSpeicher 23:30−1 min—
Wed 11 NovSpeicher 23:29−1 min—
Tue 10 NovSpeicher 23:29−1 min—
Mon 9 NovSpeicher 23:29−1 min—
Sun 8 NovSpeicher 23:29No data—
Sat 7 NovAppenzell 00:38No data—
Fri 6 NovAppenzell 00:38No data—
Thu 5 NovSpeicher 23:29No data—
Wed 4 NovSpeicher 23:29No data—
Tue 3 NovSpeicher 23:29No data—
Mon 2 NovSpeicher 23:29No data—
Sun 1 NovSpeicher 23:29No data—
Sat 31 OctAppenzell 00:38No data—
Fri 30 OctAppenzell 00:38No data—
Thu 29 OctSpeicher 23:31No data—
Wed 28 OctSpeicher 23:31No data—
Tue 27 OctSpeicher 23:31−2 min—
Mon 26 OctSpeicher 23:310 min—
Sun 25 OctSpeicher 23:31No data—
Sat 24 OctAppenzell 00:38−2 min—