The Miles Don't Double: Logging Mileage When You're Running Two Apps on the Same Drive

If you're online on Uber and Lyft at the same time, or running DoorDash and Uber Eats simultaneously, waiting to see which one pings first, you drove one set of physical miles no matter how many apps were open. Logging each app's own trip summary separately and adding them together overstates your real mileage.

Source: TruMile's guide to multi-platform gig mileage taxes and IRS Publication 463.

Why this is a different problem than "which platform paid me"

Every gig driver's income from multiple platforms lands on one Schedule C, since driving for hire is one business no matter how many 1099-NECs arrive in January. That combining problem is well covered elsewhere. The problem here is narrower and more mechanical: on the specific drives where two apps are open at once, the physical mileage happened once, and it needs to be logged once, not once per app.

Where double-counting actually creeps in

It happens when a driver manually estimates mileage per app based on that app's own trip history, rather than tracking actual GPS miles driven. A driver stacking Uber and Lyft who adds up Uber's reported trip miles and Lyft's reported trip miles separately, for hours where both apps were open and only one of them actually produced a ride, can end up with a mileage total larger than the miles the car actually traveled.

The fix: track the car, not the apps

One vehicle, one continuous GPS-tracked mileage log for the shift, regardless of how many apps are open. The business-purpose tag on each trip segment can note which app produced the eventual fare, useful for your own income analysis, but the mileage total for tax purposes comes from the actual driving, once, not from summing multiple apps' self-reported numbers.

A worked example

A driver stays online on both Uber and Lyft for a 90-minute stretch between fares, driving 30 miles total while waiting and repositioning. Both apps count that same online-and-waiting stretch as their own "online miles," since each app has no way to know the other one is open too. If the driver adds Uber's reported 30 miles for that window to Lyft's reported 30 miles for the same window, the log shows 60 miles for a single 30-mile stretch of actual driving. The car only moved 30 miles. Tracking the vehicle directly, once, avoids the double-count entirely.

What still goes on one Schedule C either way

Regardless of how many apps you stack, the combined mileage from a correctly kept single vehicle log still lands on one Schedule C as one business, the same conclusion covered in multi-platform gig mileage taxes, this just makes sure the mileage number feeding that Schedule C is accurate in the first place.

Why stacking apps does not change the online-waiting or dead-mileage rules either

A driver running two apps at once still has online-waiting time before either app produces a fare, and dead mileage between drops just the same as a single-app driver. Those categories work exactly the same way whether one app or three are open, since they describe the driver's actual physical driving, not which app happened to be active. Stacking apps changes how income gets allocated across 1099s. It does not change the underlying mileage-tracking rules at all.

Should I track mileage separately per app for my own records anyway?

You can tag trips by which app produced the fare for your own income analysis, but keep the underlying mileage total as one number derived from actual driving, not a sum of each app's self-reported figures.

Does this change which rate applies to my miles?

No, the 2026 rate still splits by the date each mile was driven, 72.5 cents through June 30 and 76 cents after, regardless of which app or apps were open during that drive.

Is it worth running more than one app at a time given this tracking complexity?

That is a business decision based on earnings, not a tax one. The tracking approach above works the same regardless of how many apps you choose to stack.

Why manual double-app tracking fails even for careful drivers

A driver running two apps at once has to make a real-time decision, mid-drive, about which app's trip the mileage belongs to, and do it consistently across dozens of overlapping trips a week. Even a genuinely careful driver will get this wrong occasionally simply because the decision has to be made instantly, without time to think it through, in the middle of an active drive with a passenger or delivery in the car.

The problem compounds over a full year of multi-apping: small, inconsistent tagging errors on individual trips average out to a log that either overstates total business mileage through double-counting, or understates it through drives that got tagged to neither app because the driver wasn't sure which one to credit. Neither error direction is defensible if the log is ever reviewed.

A single GPS-tracked log across every app you run solves the double-counting problem automatically. Try TruMile →

Related guides