Skip to contentBePünktli

172 (Innertkirchen, Grimseltor – Gadmen, Obermad)

Line 85:801:908 · PostAuto AG · bus


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

89.51% — less than 3:00 late, coverage 98.94% (floor 90%)

ThresholdShareCoverageStop events counted
under 3:0089.51%98.94%105'568
under 5:0098.14%98.94%105'568
under 15:0099.95%98.94%105'568

Distribution of delays

MeasureValue (min:s)
Median0:54
90th percentile3:03
95th percentile3:50
Measured arrivals105'568

The 3:00 threshold can see none of what happens beyond it: nine arrivals in ten are under 3:03.

Cancellations and early departures

MeasureShareCoverage
Ran rather than cancelled100%98.94%
Departures not early99.27%98.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.

DisclosureShareWhat it means
Confirmed99.21%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 timetable0.36%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 plan0.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.

MonthShareCoverageConfirmedRestated as timetableConfirmed and exactly on plan
January 202595.09%99.33%99.18%0.46%0.57%
February 202594.65%99.36%99.23%0.43%0.72%
March 202595.62%99.49%98.94%0%0.6%
April 202591.64%99.37%99.23%0.63%0.47%
May 202589.63%98.89%99.36%0.43%0.44%
June 202587.12%99.95%98.85%0.05%0.37%
July 202582.83%99.58%99.4%0.26%0.43%
August 202584.12%99.8%99.57%0.2%0.5%
September 202585.56%99.21%99.32%0.1%0.3%
October 202590.97%94.61%98.92%0%0.49%
November 202588.16%99.46%98.86%0.18%0.47%

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.

MonthShareCoverageConfirmedRestated as timetableConfirmed and exactly on plan
January 202690.86%98.51%98.74%0.45%0.59%
February 202692.8%99.31%98.92%0.24%0.53%
March 202695.93%98.08%99.24%0.17%0.81%
April 202692.54%99.14%99.23%0.35%0.63%
May 202685.97%98.59%99.61%0%0.37%
June 202689.84%99.72%99.23%0.28%0.59%
July 202687.1%99.91%99.94%0%0.32%
August 202685.37%99.38%99.51%0.22%0.36%
September 202684.6%99.63%99.69%0.02%0.48%

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

HourMonTueWedThuFriSatSunStop events counted
06:0087.83%86.87%87.41%83.47%83.43%nothing measurednothing measured6'758
07:0097.53%92.76%94.59%90.83%92.99%93.4%97.76%10'913
08:0092.49%93.24%91.37%88.19%88.45%91.13%92.16%10'520
11:0090.12%90.33%87.61%89.12%87.11%91.79%91.31%10'587
12:0089.67%89.97%84.58%90.63%84.32%89.57%88.18%10'566
13:0091.97%86.25%91.2%90.67%90.39%90.91%85.76%10'584
15:0092.91%92.28%93.52%89.9%88.35%93.2%91.97%10'700
16:0081.49%86.43%90.71%83.6%86.47%93.39%90.47%10'682
17:0090.6%85.08%91.92%89.15%89.8%86.27%88.88%10'735
18:0092.15%86.97%91.96%90.16%86.42%87.79%91.26%10'722

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 key85:801:908
Label172
OperatorPostAuto AG
Modebus

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.