R37 3360 Rochers-de-Naye – Montreux

View line R37

Rochers-de-Naye 14:27 → Montreux 15:24 Daily 0 h 57 min · 16 stops MVR

✓ Today’s run finished

Today, last fix heading to Montreux at 10:24 No data

  1. Rochers-de-Naye14:27
  2. Paccot14:42
  3. Haut-de-Caux14:49
  4. Le Tremblex15:03
  5. Glion-Alpes15:06
  6. Toveyre15:15
  7. Montreux15:24

Next service: tomorrow 14:27 from Rochers-de-Naye · Fri 6 Nov

Next departure 14:27 tomorrow · Rochers-de-Naye
On-time · 30 days
89%
25/28 runs under 3 min
RT coverage: 28 full · 0 partial · 2 no data
On-time · 90 days
92%
33/36 runs under 3 min
RT coverage: 36 full · 0 partial · 2 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: +2 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

Worst days

  • Mon 12 Oct Max en route +5 min · last fix heading to Bern +5 min
  • Thu 8 Oct Max en route +4 min · last fix heading to Bern +4 min
  • Wed 7 Oct Max en route +3 min · last fix heading to Bern +3 min

Distribution · 90 days

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

  • Early 0% · 0
  • On time 92% · 33
  • 3–10 min 8% · 3
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 80% M n=5
  • 100% T n=5
  • 83% W n=6
  • 80% T n=5
  • 100% F n=3
  • 100% S n=5
  • 100% S n=7

Stops and timetable

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

Last 90 days, 36 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
14:27on time on time
14:32≈ on time ≈ on time
14:35≈ on time ≈ on time
14:42≈ on time ≈ +1 min
14:45≈ on time ≈ +1 min
14:49≈ on time ≈ +1 min
14:50≈ on time ≈ +1 min
14:55 / 14:57≈ on time ≈ +1 min
15:03≈ on time ≈ +1 min
15:05≈ on time ≈ +1 min
15:06≈ on time ≈ +1 min
15:10 / 15:11≈ on time ≈ +1 min
15:13≈ on time ≈ +2 min
15:15≈ on time ≈ +2 min
15:18≈ on time ≈ +2 min
15:24on 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 5 NovMontreux 10:24No data—
Wed 4 NovBern 16:49+2 min+2 min
Tue 3 NovBern 16:490 min—
Mon 2 NovBern 16:490 min—
Sun 1 NovBern 16:490 min+2 min
Sat 31 OctBern 16:48−1 min—
Fri 30 OctBern 16:49No data—
Thu 29 OctBern 16:490 min—
Wed 28 OctBern 16:490 min—
Tue 27 OctBern 16:500 min+2 min
Mon 26 OctBern 16:50+1 min+1 min
Sun 25 OctBern 16:50+1 min+4 min
Sat 24 OctBern 16:51+2 min+2 min
Fri 23 OctBern 16:490 min—
Thu 22 OctBern 16:490 min+6 min
Wed 21 OctBern 16:490 min—
Tue 20 OctBern 16:490 min+2 min
Mon 19 OctBern 16:490 min—
Sun 18 OctBern 16:490 min—
Sat 17 OctBern 16:48−1 min—
Fri 16 OctBern 16:500 min—
Thu 15 OctBern 16:48−1 min—
Wed 14 OctBern 16:490 min—
Tue 13 OctBern 16:51+2 min+2 min
Mon 12 OctBern 16:53+5 min+5 min
Sun 11 OctBern 16:48−1 min—
Sat 10 OctBern 16:49−1 min—
Fri 9 OctBern 16:51+1 min—
Thu 8 OctBern 16:53+4 min+4 min
Wed 7 OctBern 16:52+3 min+3 min