30 2227 Zweisimmen – Montreux

View line 30

Zweisimmen 16:04 → Montreux 18:16 Daily 2 h 12 min · 28 stops MOB

Running now · updated 16:16

Position estimated from the timetable

Between Oeschseite and Saanenmöser 0 min

Estimated arrival at Montreux 18:16 · 24 km/h

  1. Zweisimmen16:04
  2. Oeschseite16:11
  3. Saanenmöser16:20
  4. Gstaad16:35
  5. Les Combes16:49
  6. Rossinière17:09
  7. Montreux18:16

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

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

  • Early 11% · 5
  • On time 89% · 41
  • 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=6
  • 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 (28 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 10Today
16:04on time on timePassed
16:11≈ on time ≈ on timePassed
16:20 / 16:21≈ on time ≈ on timeNext
16:24≈ on time ≈ on time
16:28≈ on time ≈ on time
16:35 / 16:36≈ on time ≈ on time
16:39≈ on time ≈ on time
16:44≈ on time ≈ on time
16:47≈ on time ≈ on time
16:49≈ on time ≈ on time
16:52≈ on time ≈ on time
16:54≈ on time ≈ on time
16:58 / 17:04≈ on time ≈ on time
17:08≈ on time ≈ on time
17:09≈ on time ≈ on time
17:14≈ on time ≈ on time
17:21 / 17:23≈ on time ≈ on time
17:28≈ on time ≈ on time
17:34≈ on time ≈ on time
17:38≈ on time ≈ on time
17:41≈ on time ≈ on time
17:47≈ on time ≈ on time
17:50≈ on time ≈ on time
17:56 / 17:58≈ on time ≈ on time
18:01≈ on time ≈ +1 min
18:05≈ on time ≈ +1 min
18:08≈ on time ≈ +1 min
18:16on time +1 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
Wed 18 NovSaanenmöser 16:14Partial coverage0 min—
Tue 17 NovChur 20:19+1 min+2 min
Mon 16 NovChur 20:180 min+4 min
Sun 15 NovChur 20:18−1 min—
Sat 14 NovChur 20:18−1 min—
Fri 13 NovChur 20:190 min—
Thu 12 NovChur 20:20+1 min+2 min
Wed 11 NovChur 20:18−1 min+4 min
Tue 10 NovChur 20:19+1 min+2 min
Mon 9 NovChur 20:190 min—
Sun 8 NovChur 20:18−1 min—
Sat 7 NovChur 20:18−1 min+2 min
Fri 6 NovChur 20:190 min—
Thu 5 NovChur 20:180 min—
Wed 4 NovChur 20:19+1 min+5 min
Tue 3 NovChur 20:190 min—
Mon 2 NovChur 20:18−1 min—
Sun 1 NovChur 20:19−1 min+2 min
Sat 31 OctChur 20:18−1 min+1 min
Fri 30 OctChur 20:18−1 min+2 min
Thu 29 OctChur 20:190 min+2 min
Wed 28 OctChur 20:190 min—
Tue 27 OctChur 20:19−1 min—
Mon 26 OctChur 20:190 min+2 min
Sun 25 OctChur 20:180 min+1 min
Sat 24 OctChur 20:190 min+2 min
Fri 23 OctChur 20:17−2 min+1 min
Thu 22 OctChur 20:21+2 min+2 min
Wed 21 OctChur 20:190 min—
Tue 20 OctChur 20:190 min—