R30 (Zweisimmen – Montreux)
Line gtfs:91-30-J-j26-1 · Montreux-Oberland Bernois · rail
Timetable period 2025
The published figure is the most recently completed timetable period. The current one is below it as a trend — month by month, and never folded into a single figure: nothing is averaged across a timetable change.
December 8, 2024 – December 13, 2025
77.83% — less than 3:00 late, coverage 97.94% (floor 90%)
| Threshold | Share | Coverage | Stop events counted |
|---|---|---|---|
| under 3:00 | 77.83% | 97.94% | 198'186 |
| under 5:00 | 82.64% | 97.94% | 198'186 |
| under 15:00 | 85.16% | 97.94% | 198'186 |
Distribution of delays
| Measure | Value (min:s) |
|---|---|
| Median | 0:45 |
| 90th percentile | 2:52 |
| 95th percentile | 4:08 |
| Measured arrivals | 169'825 |
The 3:00 threshold can see none of what happens beyond it: nine arrivals in ten are under 2:52.
Cancellations and early departures
| Measure | Share | Coverage |
|---|---|---|
| Ran rather than cancelled | 85.69% | 97.94% |
| Departures not early | 99.55% | 97.94% |
An early departure is one more than a minute ahead of the timetable. It has its own denominator — measured departures — because sharing the arrivals' one would make it depend on how many origin stops an operator has.
What this figure is made of
Three disclosures travel with every number on this page. For some operators they are not decoration — they are the whole finding.
| Disclosure | Share | What it means |
|---|---|---|
| Confirmed | 98.92% | The share of counted arrivals for which an arrival event fired (REAL). The rest is a forecast — which says something about a stop's equipment, not about whether the vehicle came. |
| Restated as timetable | 0.25% | The share of what could have been measured that was removed because the forecast was the scheduled second exactly. A denominator that lost a fifth of itself is a different statement from one that lost nothing. |
| Confirmed and exactly on plan | 0.49% | The share of confirmed arrivals filed at exactly the scheduled second. Disclosed and deliberately not removed: no rule in this project reaches this case. |
The months inside this period
The figure above is counted over the whole period. A single month inside it can have quite different coverage — and one that is below the floor on its own disappears into a period figure that clears it.
| Month | Share | Coverage | Confirmed | Restated as timetable | Confirmed and exactly on plan |
|---|---|---|---|---|---|
| January 2025 | 90.06% | 96.65% | 96.27% | 0.76% | 0.44% |
| February 2025 | 90.07% | 99.1% | 99.89% | 0.05% | 0.53% |
| March 2025 | 81.49% | 98.23% | 98.99% | 0.29% | 0.5% |
| April 2025 | 77.73% | 97.53% | 98.73% | 0.29% | 0.48% |
| May 2025 | 68.52% | 97.59% | 99.49% | 0.1% | 0.5% |
| June 2025 | 64.57% | 97.83% | 99% | 0.18% | 0.49% |
| July 2025 | 87.06% | 98.37% | 99.08% | 0.18% | 0.48% |
| August 2025 | 88.65% | 98.49% | 99.52% | 0.14% | 0.49% |
| September 2025 | 66.68% | 97.3% | 99.14% | 0.25% | 0.5% |
| October 2025 | 66.99% | 97.32% | 98.98% | 0.24% | 0.5% |
| November 2025 | 62.77% | 98.34% | 99.39% | 0.12% | 0.43% |
Rows with no share are below the 90% floor on their own. The figure above stands: it is measured over the whole period and it clears the floor. Both are true, and only one of them used to be on this page.
Trend — Timetable period 2026
The current timetable period, month by month. Each month is counted on its own; these rows do not add up to the figure above and are not meant to.
| Month | Share | Coverage | Confirmed | Restated as timetable | Confirmed and exactly on plan |
|---|---|---|---|---|---|
| January 2026 | 89.07% | 98.47% | 99.57% | 0.11% | 0.49% |
| February 2026 | 93.02% | 98.46% | 99.76% | 0.08% | 0.46% |
| March 2026 | 92.15% | 93.76% | 99.5% | 0.14% | 0.63% |
| April 2026 | 92.16% | 92.36% | 99.3% | 0.2% | 0.48% |
| May 2026 | 90.22% | 98.86% | 99.41% | 0.15% | 0.47% |
| June 2026 | not published | 83.35% | 98.85% | 0.26% | 0.38% |
| July 2026 | 92.75% | 98.11% | 99.17% | 0.45% | 0.58% |
| August 2026 | 92.54% | 98.71% | 99.73% | 0.1% | 0.45% |
| September 2026 | 92.09% | 97.4% | 98.84% | 0.33% | 0.37% |
Every row carries its own coverage. A month below the floor publishes no share — the three columns on the right still say why.
Not measured yet — these months are after the archive's most recent one: October 2026, November 2026
By hour of day
When an hour starts decides more about punctuality than almost anything else measured here.
Over the last 365 days in the archive, not the timetable year above — so the grid shows the hours as they run now.
October 1, 2025 – September 30, 2026
| Hour | Mon | Tue | Wed | Thu | Fri | Sat | Sun | Stop events counted |
|---|---|---|---|---|---|---|---|---|
| 04:00 | 90.43% | 87.6% | 87.12% | 89.03% | 87.08% | 91.74% | 91.85% | 7'673 |
| 05:00 | 88.37% | 90.16% | 88.31% | 93.06% | 87.67% | 94.23% | 94.88% | 23'720 |
| 06:00 | 87.56% | 88.72% | 85.9% | 91.5% | 90.12% | 95.5% | 95.36% | 20'560 |
| 07:00 | 83.19% | 80.11% | 81.79% | 85.63% | 84.61% | 96.43% | 96.47% | 18'495 |
| 08:00 | 87.08% | 82.82% | 86.68% | 85.29% | 87.03% | 94.3% | 96.64% | 9'512 |
| 09:00 | 76.92% | 68.27% | 75.47% | 73.08% | 74.88% | 88.94% | 90.14% | 1'464 |
| 18:00 | 87.2% | 90.9% | 91.18% | 86.88% | 84.7% | 85.01% | 92.8% | 4'922 |
| 19:00 | 87.63% | 89.17% | 90.26% | 88.45% | 83.35% | 91.76% | 92.04% | 14'016 |
| 20:00 | 85.75% | 80.85% | 87.02% | 82.49% | 88.52% | 92.14% | 88.66% | 20'915 |
| 21:00 | 82.34% | 78.31% | 83.16% | 79.24% | 89.88% | 92.21% | 82.99% | 20'438 |
| 22:00 | 78.28% | 76.65% | 77.91% | 78.83% | 93.4% | 90.11% | 80.11% | 19'891 |
| 23:00 | 79.05% | 76.82% | 77.56% | 78.11% | 93.18% | 94.42% | 78.68% | 19'742 |
| 00:00 (+1) | 79.77% | 78.51% | 80.35% | 75.39% | 92.5% | 90.69% | 79.69% | 9'002 |
| 01:00 (+1) | nothing measured | nothing measured | too few measurements | too few measurements | too few measurements | 71.31% | too few measurements | 531 |
The outlined cell is that day’s worst hour — it is not the same hour on every day.
Service day, not calendar day: hour 24 is 00:00–00:59 the following morning and still belongs to the day before.
An hour's coverage is the measurement axis alone. The figure at the top of this page takes the worst of three axes — days, journeys, measurements — and so rests on more evidence than these rows do.
About this line
| Line key | gtfs:91-30-J-j26-1 |
|---|---|
| Label | R30 |
| Operator | Montreux-Oberland Bernois |
| Mode | rail |
| Earlier keys | gtfs:91-13-Y-j23-1, gtfs:91-2T-Y-j22-1, gtfs:91-30-J-j23-1, gtfs:91-30-J-j24-1 |
A line key changes when an operator renumbers its lines or the timetable issues new identifiers. Only a succession the registry has accepted is linked here — a proposed one is not.
The line registry is built from one week of June 2026. Lines that did not run in that week have no name here — they are measured all the same.
Source and method
Source of the measurements: opentransportdata.swiss (istdaten). How we measure is written up in the methodology.
A figure is published only from 90% coverage upward. Below it there is no figure here — not a greyed-out one, not a dash, none.