Skip to contentBePünktli

Verkehrsbetriebe Luzern AG

Operator 820 · VBL · 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

80.75% — less than 3:00 late, coverage 94.03% (floor 90%)

ThresholdShareCoverageStop events counted
under 3:0080.75%94.03%21'752'176
under 5:0092.96%94.03%21'752'176
under 15:0099.32%94.03%21'752'176

Distribution of delays

MeasureValue (min:s)
Median1:27
90th percentile4:12
95th percentile5:50
Measured arrivals21'728'301

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

Cancellations and early departures

MeasureShareCoverage
Ran rather than cancelled99.89%94.03%
Departures not early99.38%94.03%

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.27%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.04%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.25%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 202581.28%92.51%99.3%0.03%0.24%
February 202581.83%92.41%99.42%0.03%0.25%
March 202580.1%92.27%99.41%0.03%0.24%
April 202578.86%92.35%99%0.06%0.23%
May 202577.9%92.47%99.15%0.05%0.23%
June 202579.76%95.73%99.45%0.03%0.25%
July 202584.96%95.91%99.54%0.02%0.29%
August 202583.54%96.05%99.41%0.03%0.27%
September 202582.59%94.81%99.37%0.03%0.25%
October 202581.95%94.39%98.54%0.09%0.25%
November 202576.62%94.19%99.41%0.03%0.22%

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 202681.41%98.63%99.32%0.04%0.23%
February 202682.86%98.6%98.97%0.05%0.26%
March 202679.1%99.66%99.28%0.04%0.23%
April 202679.65%99.59%97.99%0.05%0.24%
May 202675.52%99.6%99.31%0.04%0.23%
June 202676.16%99.62%99.26%0.04%0.23%
July 202682.12%99.7%99.36%0.03%0.26%
August 202678.02%99.69%99.3%0.05%0.23%
September 202675.73%99.69%99.34%0.04%0.22%

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
03:00nothing measurednothing measurednothing measuredtoo few measurementsnothing measurednothing measurednothing measured10
04:0093.6%93.46%93.4%86.94%93.18%88.23%74.89%47'535
05:0093.35%93.2%92.75%93.31%94.34%94.34%92.85%662'390
06:0091.71%90.43%91.15%90.96%92.3%95.03%94.71%1'354'385
07:0081.8%77.38%80.8%80.26%86.29%95.82%94.93%1'442'752
08:0076.92%70.15%76.7%74.65%81.01%91.96%89.55%1'338'691
09:0084.51%79.07%82.01%81.14%81.21%87.21%90.37%1'218'233
10:0081.33%75.94%78.79%77.62%76.33%81.18%90.27%1'208'939
11:0082.05%76.04%76.95%77.86%74.43%77.95%89.53%1'213'206
12:0083.62%79.73%77.29%81.5%76.53%81%88.97%1'227'917
13:0078.52%74.7%73.48%77.08%72.92%82.59%88.91%1'223'845
14:0080.22%77.59%73.26%78.73%72.52%80.44%86.71%1'224'538
15:0080.33%78.17%75.39%77.7%71.89%79.5%83.87%1'297'975
16:0066.26%58.55%58.69%61.85%59.88%73.74%79.61%1'449'755
17:0053.57%41.66%42.54%50.11%59.38%65.16%79.19%1'463'970
18:0078.83%66.11%65.35%72.29%77.05%77.4%85.33%1'454'404
19:0090.41%85.39%83.3%86.15%83.35%86.96%90.53%1'322'991
20:0086.86%84.18%82.7%82.07%77.47%80.27%85.37%940'031
21:0084.69%81.83%78.24%78.21%73.39%75.54%86.12%712'087
22:0089.77%86.21%82.7%81.51%74.5%75.04%93.02%664'631
23:0095.71%94.32%91.98%91.63%84.2%80.99%96.75%651'981
00:00 (+1)94.89%94.05%93.15%92.3%81.78%77.86%95.57%471'361
01:00 (+1)92.12%93.18%88.01%89.19%66.82%57.3%95.07%64'813
02:00 (+1)70.4%89.1%9.26%68.17%85.19%79.56%nothing measured50'100
03:00 (+1)99.13%100%51.81%97.01%96.57%96.46%nothing measured34'067
04:00 (+1)nothing measuredtoo few measurementstoo few measurementsnothing measured99.38%99.54%nothing measured2'602

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 operator

Operator id820
AbbreviationVBL
Modesbus
Lines in the registry32
Appears intimetable and real-time data
Country prefix85

The line registry is built from one week of June 2026; services that did not run that week are missing from it.

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.