Should you service a bike by mileage or by time?

By mileage for anything that wears from use - chain, cassette, brake pads, tires, and cables. Those parts fail because grit and load grind them down, and that's tied to miles ridden, not months on the calendar. Time only wins for parts that degrade chemically whether you ride or not, like tire rubber and tubeless sealant.

Why is mileage a better guide than a calendar for bike wear?

Because the same date means wildly different wear for different riders. A weekend rider and a bike commuter both reach 'one year' on the same day, but the commuter has put three or four times the miles through the chain. A mileage count reflects what actually wore the part; a date just guesses.

When does time matter more than mileage?

For rubber and sealant. Tires can crack and harden with age and UV even on a bike that barely moves, and tubeless sealant dries up in a few months regardless of miles. Cables and bar tape are partly time-based too, since housing corrodes and tape gets grubby and hardens over a season.

Does one mileage number fit every rider?

No, and that's the point - mileage ranges, not a single number. Dry, clean road miles are gentle; wet, gritty, or off-road miles wear parts up to three times faster. So mileage tells you far more than a date, but you still read it as a range and shorten it for harsh conditions.

Bike Service by Mileage vs Calendar (Which One Actually Tells You When)

Every "service your bike every X" rule of thumb runs into the same problem: X is usually a length of time, and time is not what wears a bike out. Grit is. Load is. A chain doesn't stretch because a year passed - it stretches because you rode it through 2,000 miles of road spray. Get that straight and most maintenance advice suddenly makes sense: track the miles, and check wear at the interval those miles suggest.

What actually wears a part out

A drivetrain wears from two things: abrasive grit working into the moving parts, and the load you put through them. Both scale with distance ridden, not days elapsed. That's why a bike hung on a garage wall for a year comes down with the same chain wear it went up with - zero new miles, zero new wear. Ride hard for a year and the same chain is finished.

The single biggest variable is conditions. A chain run dry and dirty can wear out about three times faster than the same chain kept clean and lubed. That's also why mileage is a range, never a single number: 2,000 miles of dry summer road is nothing like 2,000 miles of winter grit.

Mileage-driven vs time-driven, part by part

Not everything follows miles. A few parts age chemically whether you ride or not. Here's the honest split:

Part	Miles-driven or time-driven	Why
Chain	Miles	Stretches from grit and load; replace at 0.75% wear, roughly every 1,500-4,000 miles by conditions
Cassette	Miles	Wears with the chain; lasts about 2-3 chains if you replace chains on time
Brake pads	Miles	Friction material grinds away under braking; disc pads often 500-1,250 miles, far less when wet or hilly
Tires (tread)	Mostly miles	Tread wears with distance; road tires 2,000-4,000 miles, rear about twice as fast as front
Tires (rubber aging)	Time	Rubber cracks and hardens with age and UV even unused
Tubeless sealant	Time	Dries out in a few months regardless of miles ridden
Cables	Both	Fray and go gritty with use - every 2,000-4,000 miles - but housing also corrodes with age, so roughly annual
Bar tape	Both	Wears and gets grubby with miles, but hardens and ages over a season; often annual

Read it top to bottom and the pattern is clear. The expensive wear parts - the ones that cost you money and drop you mid-ride - are almost all mileage-driven. Time only takes over for rubber and sealant, where chemistry, not friction, is doing the damage.

Why the calendar fails you

"Change your chain every year" is bad advice because it ignores how much and where you actually ride. A weekend rider might put in 40 miles a week; a bike commuter puts in 150. Same year, same date - but the commuter hits 0.75% chain wear months earlier, and by the time the calendar says "one year" the cassette is gone too. The calendar treats both riders the same. The miles don't.

Flip it around and the calendar is just as wrong in the other direction. Tell a low-mileage rider to replace tires every 4,000 miles and they may ride cracked, aging rubber for a decade because the tread never wore out. That's the narrow slice where time genuinely wins - and it's exactly the parts, rubber and sealant, that don't care whether you ride. For the full lifespans, see how long bike parts last.

Use both, weighted right

The workable rule: service wear parts by mileage, and let time be the backstop for rubber and hygiene. Track miles on the drivetrain, brakes, and tire tread. Check age on tires and sealant. Do the general stuff - a wash, a full service once or twice a year - on a loose calendar, because dirt and neglect are partly time-based too.

The catch is that almost nobody actually counts their miles per bike. That's the gap Pedal Wrencher fills. It connects to Strava, counts the real distance on each bike - and each pair of running shoes - and emails you when a wear part is due, based on miles covered instead of a date you'd otherwise guess at. It's a reminder, not a mechanic. But it means the mileage philosophy on this page actually gets applied, instead of living in a spreadsheet you never open.