Every developer has, at some point, built a quick spreadsheet or a throwaway script to answer a question that should take thirty seconds but somehow never does. "How much will gas cost for this trip" is one of those questions. Everyone has an intuition. Almost nobody runs the actual formula.
That's a little odd, because the formula is trivial. The reason people skip it isn't the math, it's that the inputs are annoying to gather: your real MPG, the actual distance, and a current price per gallon that isn't just whatever number you remember from three months ago.
The formula, such as it is
The core calculation is one line:
cost = (distance_miles / mpg) * price_per_gallon
That's it. Distance divided by MPG gives gallons consumed, gallons times price gives dollars. If you want a round trip, double the distance or run it twice and sum. If you're comparing two vehicles, run the same distance and price through both MPG values and diff the results.
The reason this trivial formula produces wrong answers in practice isn't the arithmetic, it's bad inputs. Two of the three variables are usually wrong by default: MPG and price per gallon.
Input 1: MPG is almost never what the sticker says
The EPA rating on a car's window sticker comes from a standardized lab test cycle, not from real driving. Real-world MPG typically runs 10 to 20 percent below the sticker figure for average driving conditions, and can run further off than that for city-heavy commutes, cold climates, or an aggressive driving style.
If you're the type to log things, the accurate fix is the same one you'd apply to any noisy measurement: sample it directly instead of trusting the spec sheet. Fill up, reset the trip odometer, drive normally, fill up again, divide miles by gallons. Do that across two or three tanks and average. That gives you an empirical MPG instead of a lab-derived one, and it's usually a meaningfully different number.
fueleconomy.gov, run by the EPA and Department of Energy, also publishes a community-reported "your MPG" field alongside the official rating for most vehicle models, aggregated from thousands of owner logs. Useful as a starting estimate if you haven't measured your own yet, though it's still an average across a population, not you specifically.
Input 2: price per gallon needs to be current, not remembered
Gas prices swing by state, by county, and sometimes by 20 to 30 cents within the same metro area depending on the station. Plugging in "whatever I paid last time" introduces error that has nothing to do with your driving and everything to do with stale data.
The EIA's weekly gasoline price data is the more authoritative, slower-moving source, broken out by region, useful for a general sense of the trend. For a same-day number, a live tracker along your actual route is more accurate than a national or even statewide average, especially for a multi-state trip where prices can shift meaningfully between the start and end of your route.
A minor complication: MPG and cost per mile aren't linear
One thing that trips people up when they start comparing vehicles is assuming fuel cost scales linearly with MPG. It doesn't, because MPG itself is already an inverse ratio (miles per unit of fuel), so the actual cost curve flattens out at higher MPG values and gets steep fast at lower ones.
Going from 15 MPG to 20 MPG saves you more money per mile than going from 40 MPG to 45 MPG, even though both are "5 MPG improvements." At 15 MPG you're burning 6.67 gallons per 100 miles; at 20 MPG you're down to 5 gallons per 100 miles, a real drop of 1.67 gallons. At 40 MPG you're burning 2.5 gallons per 100 miles; at 45 MPG it's 2.22 gallons, a drop of only 0.28 gallons. Same nominal MPG gain, wildly different fuel savings. If you're building any kind of "upgrade your vehicle" comparison tool, converting to gallons per 100 miles (or liters per 100 km if you're going metric) before comparing is the correct move, not comparing raw MPG numbers directly.
Where the one-liner formula breaks down
The single-line formula assumes constant MPG across the whole trip, which is fine for a rough estimate and wrong for anything more precise. Real trips are a mix of segments: highway cruising, city stop-and-go, maybe a mountain pass. Each segment has a meaningfully different effective MPG, and averaging them naively (just using one blended MPG for the whole distance) undercounts the cost of the inefficient segments.
A slightly better model splits the trip into segments and sums:
total_cost = sum(
(segment_distance / segment_mpg) * price_per_gallon
for segment in trip_segments
)
This matters more than it sounds like it should. City driving in traffic can run 20 to 30 percent worse fuel economy per mile than steady highway cruising, because of constant acceleration from stops. If a third of your trip is through a congested urban corridor, treating that third with your highway MPG number will meaningfully undercount the actual cost. The Wikipedia entry on fuel economy in automobiles has more background on why city and highway driving produce such different real-world numbers.
Building this yourself vs just using a calculator
If you want to run this in a spreadsheet or a five-line script, go for it, the formula above is genuinely all it takes for a single-segment estimate. Where it gets more annoying is wiring in live gas price data and handling multi-vehicle comparisons cleanly without copy-pasting the same block three times with different numbers swapped in.
For a version that's already wired up, the free fuel cost calculator by EvvyTools takes distance, MPG, and price per gallon and returns the total, with support for comparing two vehicles side by side on the same trip. It's the same formula from above, just without needing to open an editor for a thirty-second question. The rest of EvvyTools' calculator tools, covering everyday math beyond fuel costs, are at https://evvytools.com if the trip planning spreadsheet you're building needs a few more building blocks.
The longer writeup on the full trip-cost formula, including how to handle unit conversions between metric and imperial and how rideshare or delivery drivers should think about the same math differently, is in the guide on calculating real fuel costs.
Rideshare and delivery driving is the same formula with a different denominator
If you drive for a rideshare or delivery platform on the side, the fuel cost formula is identical, but the number you actually care about shifts from "total trip cost" to "cost per dollar earned." A shift that nets $180 in fares but burns $35 in gas at your real MPG and local price is netting $145 before any other expenses, and that fuel percentage (about 19 percent of gross in this example) is worth tracking over time rather than recalculating from scratch every shift.
def net_after_fuel(gross_earnings, miles_driven, mpg, price_per_gallon):
fuel_cost_value = fuel_cost(miles_driven, mpg, price_per_gallon)
return {
"gross": gross_earnings,
"fuel_cost": fuel_cost_value,
"net": round(gross_earnings - fuel_cost_value, 2),
"fuel_pct_of_gross": round((fuel_cost_value / gross_earnings) * 100, 1)
}
Tracking fuel_pct_of_gross over several weeks tells you something a single shift's number can't: whether a bad night was a fluke (surge pricing offset high mileage) or a pattern (you're driving a lot of empty miles between fares, which quietly eats margin the same way an inefficient query eats compute budget without showing up anywhere obvious).
The part that actually matters
None of this is complicated math. A junior dev could implement the core formula correctly on the first try. The failure mode isn't the arithmetic, it's skipping the measurement step and plugging in stale or optimistic numbers because gathering the real ones felt like more friction than the question was worth.
The same discipline that makes for good input validation in code applies here: garbage in, garbage out. A perfectly correct formula fed a sticker MPG and a three-month-old gas price will confidently produce a wrong answer. Spend the extra two minutes getting real inputs and the trivial formula suddenly gives you a number worth trusting.
Quick reference
For anyone who wants the condensed version to paste into a notes app before their next trip:
- Measure your real MPG over a tank or two, don't trust the sticker.
- Get a current price per gallon along your actual route, not a remembered number.
- Split multi-terrain trips into segments if you want precision beyond a rough estimate.
- Multiply, sum, done.
It's a thirty-second calculation once the inputs are right. Getting the inputs right is the only part worth spending real time on.
Top comments (0)