R30 2206 Montreux – Zweisimmen

View line R30

Montreux 05:37 → Zweisimmen 07:56 Daily 2 h 19 min · 33 stops MOB

✓ Today’s run finished

Today it reached Zweisimmen at 07:56 0 min

  1. Montreux05:37
  2. Planchamp05:43
  3. Les Avants06:03
  4. Montbovon06:34
  5. Château-d'Oex La Palaz07:00
  6. Gstaad07:21
  7. Zweisimmen07:56

Next service: tomorrow 05:37 from Montreux · Mon 16 Nov

Next departure 05:37 tomorrow · Montreux
On-time · 30 days
100%
30/30 runs under 3 min
RT coverage: 30 full · 0 partial · 0 no data
On-time · 90 days
98%
48/49 runs under 3 min
RT coverage: 49 full · 0 partial · 0 no data
Typical delay
−1min
Median at arrival, 90 days
30 days: −1 min
P90
+2min
9 in 10 runs arrive with less than this
30 days: +1 min

Last 30 days

Arrival delay at Zweisimmen, 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 19 Aug Max en route +3 min · last fix heading to Gfeld +3 min

Distribution · 90 days

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

  • Early 35% · 17
  • On time 63% · 31
  • 3–10 min 2% · 1
  • 10–30 min 0% · 0
  • 30+ min 0% · 0

On-time by weekday

  • 100% M n=7
  • 100% T n=6
  • 86% W n=7
  • 100% T n=6
  • 100% F n=7
  • 100% S n=8
  • 100% S n=8

Stops and timetable

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

Last 90 days, 49 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
05:37+1 min +1 min
05:38≈ +1 min ≈ +1 min
05:39≈ +1 min ≈ +1 min
05:40≈ +1 min ≈ +1 min
05:42≈ +1 min ≈ +1 min
05:43≈ +1 min ≈ +1 min
05:44≈ +1 min ≈ +1 min
05:47≈ +1 min ≈ +1 min
05:49≈ +1 min ≈ +1 min
05:54 / 05:55≈ +1 min ≈ +1 min
05:58≈ +1 min ≈ +1 min
06:03≈ +1 min ≈ +1 min
06:06≈ on time ≈ +1 min
06:11 / 06:14≈ on time ≈ +1 min
06:18≈ on time ≈ +1 min
06:27 / 06:29≈ on time ≈ +1 min
06:34 / 06:37≈ on time ≈ +1 min
06:41≈ on time ≈ +1 min
06:47≈ on time ≈ +1 min
06:48≈ on time ≈ +1 min
06:54 / 06:59≈ on time ≈ +1 min
07:00≈ on time ≈ +1 min
07:02≈ on time ≈ +1 min
07:04≈ on time ≈ +1 min
07:07≈ on time ≈ +1 min
07:11≈ on time ≈ +1 min
07:16 / 07:17≈ on time ≈ +1 min
07:21 / 07:25≈ on time ≈ +1 min
07:29≈ on time ≈ +1 min
07:34≈ on time ≈ +1 min
07:39≈ 1 min early ≈ +1 min
07:45≈ 1 min early ≈ +2 min
07:561 min early +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
Sun 15 NovZweisimmen 07:570 min—
Sat 14 NovTrogen 21:520 min—
Fri 13 NovTrogen 21:52−1 min—
Thu 12 NovTrogen 21:49−1 min—
Wed 11 NovTrogen 21:52−1 min—
Tue 10 NovTrogen 21:52−1 min—
Mon 9 NovTrogen 21:50−1 min+2 min
Sun 8 NovTrogen 21:54+2 min+2 min
Sat 7 NovTrogen 21:49−1 min—
Fri 6 NovTrogen 21:52−1 min—
Thu 5 NovTrogen 21:52−1 min+3 min
Wed 4 NovTrogen 21:52−1 min+4 min
Tue 3 NovTrogen 21:52−1 min—
Mon 2 NovTrogen 21:53−1 min+2 min
Sun 1 NovTrogen 21:53−1 min—
Sat 31 OctTrogen 21:54+1 min+2 min
Fri 30 OctTrogen 21:530 min—
Thu 29 OctTrogen 21:52−1 min—
Wed 28 OctTrogen 21:52−1 min—
Tue 27 OctTrogen 21:55+2 min+3 min
Mon 26 OctTrogen 21:53−1 min—
Sun 25 OctTrogen 21:530 min+3 min
Sat 24 OctTrogen 21:51−1 min—
Fri 23 OctTrogen 21:52−1 min+3 min
Thu 22 OctTrogen 21:56+3 min+3 min
Wed 21 OctTrogen 21:52−1 min—
Tue 20 OctTrogen 21:530 min—
Mon 19 OctTrogen 21:52−1 min—
Sun 18 OctTrogen 21:53−1 min—
Sat 17 OctTrogen 21:530 min—