Reference
Where these numbers come from
Every service interval in Loam comes from the component manufacturer's own documentation wherever one publishes a figure. Where nothing is published, the app carries a conservative estimate and says so in the same breath as the number. It never invents a manufacturer figure, and it never presents a guess as a schedule.
The order of preference
A service clock is only as good as the number behind it, so the dataset applies the same order every time.
| Source | How it is treated |
|---|---|
| Manufacturer service documentation | Used as published, per model year. This is the default and covers most of the dataset. |
| Manufacturer publishes a range | The shorter end is used. A clock that comes due early costs a check; one that comes due late costs a part. |
| Dealer or workshop convention, no published figure | Carried and labelled as a convention, not as a manufacturer schedule. |
| Nothing published anywhere | A conservative estimate, labelled an estimate on the page and in the app. |
| Sources disagree | Both figures are shown, and the disagreement is stated rather than resolved. |
What "conservative" actually means
It means the app would rather tell you to look at something you did not need to look at than stay quiet while a part wears past its limit. Two consequences worth knowing about:
- Where a manufacturer gives a window, Loam uses the near edge. RockShox publishing 100 to 200 hours for a full service becomes a 100 hour clock.
- Some parts can never show red on distance alone. Brake pads and cassettes wear at a rate that depends on grit, weather and how you brake, none of which the app can see, so distance moves them to amber as a prompt to look and no further. A red light you cannot trust teaches you to ignore red lights.
Model year is part of the figure
Service intervals are not stable per brand, so storing one number per brand would be wrong more often than right. Two examples the dataset carries explicitly:
- RockShox changed service kits around 2023, and the pre- and post-2023 figures differ.
- KTM and Husqvarna model year 2024, the TPI to TBI change, moves nearly every engine figure.
Where a figure depends on a model year the app cannot infer, it asks you to confirm the year rather than guessing on your behalf.
Hours, distance, rides and months are different clocks
Suspension is specified in hours, drivetrain wear in distance, fluids in months, and some parts in ride count. Loam runs whichever clocks a manufacturer actually specifies for that component and shows the one that comes due first. It does not convert between them, because a conversion would be a number nobody published.
Full interval tables are in the MTB service interval guides and the moto service interval guides, with the figures per manufacturer and tier.
What Loam will not do
- Fabricate a manufacturer figure. If a brand publishes nothing, the page says so.
- Present an estimate as a schedule. The label travels with the number, in every language.
- Resolve a real disagreement silently. Both numbers, plus the fact that they conflict.
- Invent wear you have not ridden. An unknown state stays unknown; the app does not backfill a plausible-looking history.
Corrections
September 2026 - hours on Bosch-connected bikes were wrong, and this page's own rule is what they broke.
From version 2.4.0 to 2.11.2, on bikes connected to a Bosch eBike system, Loam used the drive unit's total operating hours as the wear clock. That figure counts every hour the system was switched on, standby included. FOX and RockShox specify their intervals in riding hours, so every hours-based interval - fork lowers, full service, dropper - ran roughly four times fast. On the bike that surfaced it, 939 recorded hours against 3,667 km works out at 3.9 km/h, while that rider's own ride list averages 16.6 km/h. The real riding time was about 196 hours.
The clock was inflated, so parts read more worn than they were and services came due early. Nobody was told a worn fork was fine. The cost was servicing far more often than needed, and a service record whose hours were not real - which matters most at resale, since 2.11.2 is the release that started printing where each reading came from.
Only Bosch-connected bikes were affected. A bike fed by Strava, by imported files, or by a manual odometer never took its hours from a motor.
Fixed in 2.11.3. Hours now come from rides - Strava's per-ride moving time where the bike is also Strava-linked, otherwise the bike's own Bosch activity feed. Existing bikes correct themselves on the next sync: the clock and every service baseline are rebuilt from the rider's own ride history, so a service logged in April keeps the wear it really has. Distance and the rider's own service log are untouched.
It is written here rather than quietly fixed because the rule it broke is on this page. "Invent wear you have not ridden" is listed above as something Loam does not do, and counting standby hours as wear is exactly that. A page claiming a standard is worth less than a page that says when it failed to meet one.
If a figure here is wrong, or a manufacturer has published something newer, tell us and it gets fixed in the dataset rather than argued about. The interval data is versioned with the app and served to existing installs, so a correction reaches riders without waiting for a release. Mail support@loamlog.com, or use suggest a component or interval.
FAQ
Where do Loam service intervals come from?
From the component manufacturer's own service documentation wherever one publishes a figure: FOX, RockShox, Öhlins, DVO, EXT, Cane Creek, Formula, SRAM and Shimano on the bike side, and KTM, Husqvarna, WP, KYB, Showa, Sur-Ron and Talaria on the moto side. Where a manufacturer publishes nothing, the figure is a conservative estimate and is labelled as one.
What if the manufacturer and my dealer disagree?
Both figures are kept and the disagreement is stated. The moto engine guide is the clearest example: a dealer cadence circulates that is far shorter than the manual's figure, and the guide gives both rather than picking one for you.
Can I see the source for a specific interval?
Ask and we will point you at it. Per-figure citations are being added to the dataset itself so the source travels with the number instead of living in our notes; until that lands, mail support@loamlog.com with the component and we will tell you exactly where the figure came from.
Put your next service on a real clock
Loam turns your actual ride hours and distance into a service clock for every component, measured against these intervals. Local-first, no account.
