R30 2440 Château-d'Oex – Gstaad

View line R30

Château-d'Oex 00:04 → Gstaad 00:26 Daily 0 h 22 min · 8 stops MOB

✓ Today’s run finished

Today, last fix heading to Gstaad at 00:27 No data

  1. Château-d'Oex00:04
  2. Château-d'Oex La Palaz00:05
  3. Les Granges-Gérignoz00:07
  4. Flendruz00:12
  5. Rougemont00:16
  6. Saanen00:21
  7. Gstaad00:26

Next service: tomorrow 00:04 from Château-d'Oex · Tue 17 Nov

Next departure 00:04 tomorrow · Château-d'Oex
On-time · 30 days
100%
7/7 runs under 3 min
RT coverage: 7 full · 0 partial · 18 no data
On-time · 90 days
96%
27/28 runs under 3 min
RT coverage: 28 full · 0 partial · 26 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: +2 min

Last 30 days

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

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

Worst days

  • Sun 11 Oct Max en route +45 min · last fix heading to Gstaad +45 min

Distribution · 90 days

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

  • Early 4% · 1
  • On time 93% · 26
  • 3–10 min 0% · 0
  • 10–30 min 0% · 0
  • 30+ min 4% · 1

On-time by weekday

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

Stops and timetable

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

Last 90 days, 28 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
00:04on time on time
00:05≈ on time ≈ on time
00:07≈ on time ≈ on time
00:09≈ on time ≈ on time
00:12≈ on time ≈ on time
00:16≈ on time ≈ +1 min
00:21 / 00:22≈ on time ≈ +1 min
00:26on 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
Mon 16 NovGstaad 00:27No data—
Sun 15 NovGstaad 00:27No data—
Sat 14 NovGstaad 00:27No data—
Fri 13 NovParis-Est 16:23No data—
Thu 12 NovParis-Est 16:39No data—
Wed 11 NovParis-Est 16:39No data—
Tue 10 NovParis-Est 16:39No data—
Mon 9 NovParis-Est 16:39No data—
Sun 8 NovParis-Est 16:09No data—
Sat 7 NovGstaad 00:27No data—
Fri 6 NovParis-Est 16:23No data—
Thu 5 NovParis-Est 16:39No data—
Wed 4 NovParis-Est 16:39No data—
Tue 3 NovParis-Est 16:39No data—
Mon 2 NovParis-Est 16:39No data—
Sun 1 NovGstaad 00:27No data—
Sat 31 OctGstaad 00:27No data—
Fri 30 OctGstaad 00:27No data—
Thu 29 OctGstaad 00:26−1 min—
Wed 28 OctGstaad 00:270 min—
Tue 27 OctGstaad 00:270 min—
Mon 26 OctGstaad 00:26−1 min—
Sun 25 OctGstaad 00:27+1 min—
Sat 24 OctGstaad 00:30+3 min+3 min
Sun 18 OctGstaad 00:28+1 min+2 min
Sat 17 OctGstaad 00:270 min—
Sun 11 OctGstaad 01:12+45 min+45 min
Sat 10 OctGstaad 00:27−1 min—
Sun 4 OctGstaad 00:27+1 min—
Fri 2 OctGstaad 00:25+1 min+2 min