Last reviewed: August 3, 2026 · By the RaceYear team
Short answer: Race car maintenance tracking software has to count something other than miles, because a race car has no working odometer and never sees a public road. Track part life by laps, race nights, heat cycles, run hours or calendar date — one unit per component, whichever one actually wears that part out.
Key takeaways
Everybody tries the free app first. You download something with a wrench icon, punch in the race car, and the setup wizard asks for your odometer reading. You type 0, because that’s the truth, and then the app spends the rest of the season telling you the oil change is due in 3,000 miles. Two years later it still says 3,000 miles. Meanwhile you’ve put 900 laps on a motor and you’re guessing. Here is how to build a counting system that actually works on a car that gets towed everywhere it goes.
Because the trigger is a number that never changes. Consumer maintenance apps are built around an odometer reading you update yourself, and a race car’s odometer is either disconnected, missing, or sitting on a dash that only has a tach and an oil pressure gauge. The countdown never counts down.
Look at what the popular apps ask you for. CARFAX Car Care, at over a million installs on Android, offers to “Update your car’s odometer reading” and to tell you “when your car is due for service work on oil, tires, filters and inspections” (CARFAX Car Care on Google Play). Drivvo shows its reminder as a distance countdown — “Service in 500 km” (Drivvo). Both are good tools. Both are built on a meter your race car doesn’t have.
It isn’t a bug and it isn’t laziness on the developers’ part. It’s a units problem. On a street car, miles are a decent proxy for the things that actually wear parts out: revolutions, heat, load cycles. On a race car, miles aren’t a proxy for anything, because nobody is counting them.
| What a maintenance app assumes | Your tow rig | Your race car |
|---|---|---|
| A meter that keeps climbing | Odometer, updated at the pump | No odometer; the car rides to the track on a trailer |
| A service trigger | “Service in 500 km” counts down | Never fires, because the reading never moves |
| What causes the wear | Road miles | Laps, heat cycles, race nights, run hours |
| What the life belongs to | The vehicle | The part, which moves between cars |
Racers have been chasing this for over a decade. A 2013 thread on the Autosport forums opens with a racer asking for software to keep track of “the accumilated ,ileage of parts on a race car” with “pre-determined mileage limits, life-out predictions etc.” The best answer he got, from somebody who had clearly done it: “Simply write it down when items serviced…the cost is a biro and an exercise book” (Autosport Forums). The notebook guy is right about the discipline and wrong about the ceiling. You just need the right column headings.
It should count a different thing for every kind of part, and let you say which. Maintenance-management practice already has names for this. FTMaintenance defines usage-based maintenance as “Maintenance scheduled based on measured usage or meter reading values,” time-based maintenance as “Maintenance scheduled using fixed time intervals without considering how much the asset has been used,” and condition-based maintenance as work performed “only when there are signs of imminent failure” (FTMaintenance). A race car needs all three running at the same time, on different parts.
There are five meters worth keeping on a race car, and only one of them is a number of miles:
Here’s the test that keeps you honest: would the interval still be true if you changed tracks? An oil change every three races survives a move from a quarter-mile to a half-mile, because it’s really about heat and time at temperature. A 300-mile valve spring interval does not — at the quarter-mile, that’s twice as many laps as it is at the half. If the number doesn’t survive the move, it belongs in laps, not in events.
Match the meter to the wear. The table below pulls real published intervals from manufacturers, retailers and trade press. Every one of them comes from a specific class on a specific kind of track, so treat them as the shape of the answer, not as your answer.
| Component | Count it by | Published intervals actually in print | What moves the number |
|---|---|---|---|
| Engine oil | Race nights | Sprint car: “Change oil (3 races)” (Speedway Motors). 600cc micro sprint: every 3–4 races on regular oil, every 6 on Motul 300V or similar synthetic (Hyperracing) | Oil grade, fuel type, water in the oil, how many features you ran |
| Shocks | Races | Service “about every 20-25 races” (Speedway Motors) | Track roughness, races per season, whether you run a rough cushion |
| Valve springs | Race miles → laps | Dirt late model: changed “at the 300-mile mark” (Engine Builder) | RPM ceiling, spring package, class rules |
| Engine refresh or rebuild | Race miles or season | Dirt late model: “600+ miles before a rebuild, typically” (Engine Builder). Sealed 602 crate: “easily lasting an entire season” on light service (Speedway Motors) | Open vs. sealed class, budget, whether you chase a championship |
| Front wheel bearings, king pins | Races | Micro sprint: repack fronts every 4 races; replace king pins and bushings every 25 races (Hyperracing) | Dirt vs. asphalt, water on the track, pressure washing habits |
| Tires | Heat cycles | No universal count published; tires need “a minimum of 24 hours to relax” after a heat cycle (Tire Rack) | Compound, track prep, ambient temp, how you scuff |
| Valve lash, small fasteners | Run time and sessions | Briggs 206: valve lash “checked during the first 30-60 minutes of initial run time”; exhaust fasteners “Every time you come off of the track” (Briggs Racing) | New engine vs. settled engine, vibration, class |
| Belts, fuel cell, head-and-neck restraint | Calendar | SFI: restraint assemblies 2 years; Spec 28.1 fuel cells “5 Years + 2 Year Recert”; head and neck restraints 5 years | Nothing. The date on the tag is the date |
Notice what happens when you read across that table: the published sources don’t even agree on the unit. Engine Builder writes dirt late model engine life in miles. Hyperracing writes micro sprint life almost entirely in races. Speedway Motors writes shocks in races, and its sprint car checklist writes oil in races. Briggs Racing writes kart valve lash in minutes of run time. Nobody writes any of it in odometer miles, and no two classes count the same way.
They disagree inside a single source, too. Hyperracing’s oil interval doubles — 3–4 races to 6 races — purely on which oil you pour in. Speedway’s shock article gives 20–25 races and then, a paragraph later, concedes that “some racers may only race 20-25 races a season and can sometimes make it through a whole season,” while others “can race up to 60-70 races a season and should have them checked accordingly.” That is not sloppiness. It’s an honest admission that a race is not a fixed quantity of wear. Which is exactly why your log has to hold the raw counts, not just the reminders.
Divide the published miles by your track’s length in miles. That’s the whole conversion, and it is the single most useful piece of arithmetic in this post, because it lets you use engine-builder numbers on a car that has no odometer.
| Published interval | 1/4-mile track | 3/8-mile track | 1/2-mile track |
|---|---|---|---|
| 300 race miles (dirt late model valve springs) | 1,200 laps | 800 laps | 600 laps |
| 600 race miles (dirt late model rebuild) | 2,400 laps | 1,600 laps | 1,200 laps |
Two honest caveats. Advertised track length is a marketing number as often as it’s a survey, and if you run five different tracks you are averaging anyway — so keep the laps by track if you can, and accept the error if you can’t. And hot laps count. A car that runs hot laps, a heat race, a consi and a feature has four sessions of wear on it, not one, and the sessions nobody scores are the ones that vanish from a log.
Counting the laps themselves is its own small discipline — we walked through the whole method in Every Lap Counts: The Smart Way to Maintain Your Race Car, and the structure of a typical night is broken down in our guide to race night format. The short version: write the lap count of every session on the same sheet you already fill out, before you load the car.
Start with somebody else’s number, convert it to your meter, then let your own findings move it. In order:
And the rule that breaks most software: the life belongs to the part, not to the car. Move a rear end to the backup car and its laps go with it. Sell a set of shocks and their history should go with them. Sanctioning-legal or not, a set of springs that lived on a spare chassis all spring didn’t reset when it got bolted to the primary.
The two motorsport-specific tools that rank for this get that right, which is why they exist at all. PitLogic stores per part “the number of laps, events, and condition so that you know when it’s time to change it out,” and adds session laps to the parts you were running (PitLogic). Trackit pitches the same idea from the professional end: “Every part has a max life. trackit tracks it automatically” (Trackit). Neither one is asking for your odometer.
Enough that a stranger could rebuild the season from it. A race car maintenance log has one job the setup sheet doesn’t: it has to survive being wrong. Log these, every night, in this order:
Motorstate’s spring checklist is a good reminder that some of this only happens once a year: cut the oil filter open and check it for debris “a couple times each year,” clean or replace the fuel filter and inspect the fuel lines “as part of an annual maintenance routine, if not more often,” and change transmission fluid “periodically” (Motorstate). A log that only has race nights in it will quietly skip every annual job you own.
For the tow vehicle and the trailer, absolutely — those have real road miles and a real odometer, which is exactly the case consumer apps were built for. A dually that pulls 12,000 miles a season is the textbook use case for a distance countdown, and CARFAX Car Care or Drivvo will do that job better than any racing tool.
Trailer bearings, trailer tires and brake controllers all live on a mix of road miles and calendar age, so a general app handles them cleanly. And there’s a bonus: the mileage log you keep for the tow rig is the same record you need at tax time, which we cover in the racing mileage deduction guide.
The line is simple. If the vehicle drives itself to the event, use a mileage app. If it rides there on a trailer, you need something that counts laps. Most racers end up running both, and that’s fine — the truck’s app and the race car’s log are answering different questions.
You can enter the car, but the reminders won’t work. Consumer apps like CARFAX Car Care are built around an odometer reading you update, and Drivvo counts down to service in kilometers. A race car’s odometer never moves, so every countdown sits still. Use those apps for the truck and the trailer, and count laps, races or heat cycles for the race car.
Write the lap count of each session on the same sheet you already fill out. Most weekly shows post the scheduled distance for hot laps, heats and the feature, so you’re recording a planned number and correcting it when a race gets shortened. Add the sessions up at the end of the night and carry one running number forward. A phone note beats a perfect system you don’t use.
By laps for anything that wears as it turns — bearings, rings, springs, chains, brake rotors. By races for services tied to a night rather than a distance, like an oil change or repacking front hubs. Speedway Motors publishes shock service at every 20 to 25 races; Hyperracing publishes micro sprint king pins at every 25 races. Both are counts of events, not distance, and both assume a normal night.
Set your own and treat the first one as a guess. Pick the unit that drives the wear, pick a conservative number, and inspect at half of it. Write down what you find every single time you look. After a season you’ll have real data for your class, your track and your driver, which beats any published number written for somebody else’s car.
The part. A rear end that moves to the backup car takes its laps with it, and a set of shocks you sell still has a history the buyer should get. That’s why a race car logbook app that only tracks vehicles falls apart the first time you swap something. Trackit sells that idea directly: every part has a max life, and the software tracks it.
You can absolutely do every bit of this by hand. A composition book with track length, session laps and a parts page will run a championship-winning program, and plenty of them have. The counting isn’t hard. Doing it at 11:40pm in the trailer, every week, for eight months, and then remembering in July which set of shocks got freshened in April — that’s the part that breaks. RacePrep was built for exactly the workflow this post just described:
Start tracking part life by laps in RacePrep — there’s a free demo mode, so you can see your own numbers before you commit a season to it. Then dig into how long the parts should last in the first place with How Long Do Race Car Parts Last, and build the routine around it with the weekly race car maintenance checklist.
Tripped over a term in here? Every one of them is spelled out in the RaceYear racing glossary.
Setup notes, maintenance logs, race-day plans, and tax tracking — all in your pocket.
Get the apps