Every petrol pump in India has been dispensing E20 since 1 April 2026, which means any mileage number you recorded before that date is now a different baseline. Here is a structured two-tank experiment that tells you precisely what changed for your vehicle, not the national average.
The debate about E20's effect on fuel economy generates a lot of national averages. Government roadmap estimates put the consumption increase at roughly 1–2% for vehicles tuned for the new blend and up to 6–7% for older vehicles calibrated on earlier blends. Controlled test-agency results published in mid-2026 measured 2–6% higher consumption against E10 across vehicles three to ten years old. Those are useful ranges, but they cannot tell you whether your particular vehicle, with your tyre pressure, your city's traffic pattern, your driving style, lands at 2% or at 6%.
The only way to know is to measure it yourself, tank to tank, with a controlled protocol. This post lays out exactly how to do that.
Why "My Mileage Feels Different" Is Not a Data Point
Human mileage intuition is genuinely bad. Fill-up intervals vary, odometer resets get forgotten, and a single tank that happened to include a 90-minute traffic jam on the way to a wedding will skew your sense of things for weeks. Before you can measure any E20 effect, you need to understand what makes a mileage number valid.
Tank-to-tank is the standard: you fill to the brim, reset your trip meter, drive until you need to fill again, return to the same pump, fill to the brim a second time, and divide kilometres by litres. That is the only method that sidesteps the dashboard computer's tendency to read 5–15% optimistically, something worth understanding before you start (see why your dashboard average lies for the mechanics of that gap).
A single tank-to-tank reading has more signal than any dashboard average, but it still has noise: a headwind, an unusually hot day with more AC use, one fast highway run mixed into an otherwise city-heavy tank. Two consecutive tanks under matched conditions reduce that noise considerably. Three is better. This experiment uses two as the minimum viable signal.
Setting Up the Experiment
The goal is to isolate the E20 variable as much as possible. You cannot go back in time and run pre-E20 tanks with perfect conditions, but you can set up two consecutive matched tanks and compare them to your pre-April 2026 log, if you have one. If you do not have historical data, the two-tank run still gives you a stable current baseline that you can track going forward.
What to Control
Before starting, note down these values and keep them unchanged across both tanks:
- Tyre pressure: Check and set to the manufacturer's recommended cold pressure before Tank 1. Do not adjust between tanks.
- Route: Use a route you drive every week, your commute, a familiar city loop. Not a highway run if your baseline was city, not a mix if your baseline was pure highway.
- AC usage: Either always on or always off across both tanks. AC typically costs 1–2 km/l in city traffic; inconsistency here will swamp the E20 signal.
- Load: Same passengers, same boot weight roughly. A second occupant and a boot full of luggage can shift mileage by 3–4%.
- Time of day: If you can, run both tanks across the same types of days, weekday commute patterns have different stop-start ratios than Sunday drives.
You are not trying to run a lab experiment. You are trying to reduce the noise enough that a real signal shows through. Controlling these four variables does that.
The Fill Protocol
At the start of Tank 1: go to your regular pump, fill to the first automatic cut-off (do not top up repeatedly, each pump cuts off at a slightly different point, so standardise on the first click). Reset your trip meter to zero. Note the total amount paid in ₹ and the litres dispensed.
Drive normally across your controlled route until the fuel warning light or your gauge tells you it is time to fill. Return to the same pump, pump consistency matters because different pumps at the same station can have small calibration differences. Fill again to the first automatic cut-off. Record litres and ₹.
This is Tank 1's data: kilometres on the trip meter divided by litres dispensed gives you km/l. Amount paid divided by kilometres gives you ₹/km.
Immediately begin Tank 2 with the trip meter reset and the same protocol. Two tanks of matched data is your baseline.
Running the Numbers
Say your tank holds roughly 40 litres and you drove 480 km before refilling. That is 12.0 km/l. Your second tank: 470 km, same 40 litres, 11.75 km/l. Average of the two: 11.9 km/l. That is your current E20 real-world number for this vehicle, this route, this season.
Now you need a comparison. If you logged fill-ups before April 2026 using the same tank-to-tank method, pull those numbers. A cluster of five to eight tanks from, say, January to March 2026 gives you a reliable pre-E20 reference for this vehicle. If that average was 13.0 km/l and your current average is 11.9 km/l, the difference is 1.1 km/l, or roughly 8.5%, above the upper end of the measured range, which is a flag worth investigating (tyre pressure, air filter, throttle body fouling).
If your previous average was 12.3 km/l and your current is 11.9, that is 3.3%, well within the measured range for your vehicle's age category. Note it, track it, move on.
The ₹/km number is often more actionable than km/l. If petrol in your city is ₹104 per litre and you are getting 11.9 km/l, your fuel cost is ₹8.74 per km. At a hypothetical pre-E20 figure of 13.0 km/l it would have been ₹8.00 per km. On a 1,500 km month that is ₹1,110 more per month from the mileage shift alone, not counting any price change at the pump. That is the number worth knowing.
Bharometer
Log every fill-up, scan the pump screen to skip typing, and see your real tank-to-tank km/l and ₹/km automatically, so your two-tank E20 experiment has a permanent, searchable home.
Where to Log This So the Data Is Actually Useful
A notebook works for one experiment. It does not work for six months of tracking. The value of this exercise compounds when you can look back at a series of tanks, see a trend line, and catch the moment your mileage starts drifting further than the E20 baseline, because that drift is almost certainly something mechanical: a partially clogged fuel injector, a worn spark plug, dropping tyre pressure. A fuel log that exists only in your memory or on a petrol receipt in the glovebox is invisible as a diagnostic tool.
Bharometer handles the logging side: log a fill-up in seconds, and the pump-scan feature photographs the pump screen and auto-fills litres, amount, and rate so you are not typing at a busy forecourt. Every tank is stored on-device with no account required, and the app computes tank-to-tank km/l automatically from what you enter. The cost per kilometre is calculated per tank and across any date range you want to review.
For the two-tank experiment specifically: log Tank 1 as you would any fill-up. Then log Tank 2. The app will show you both tanks side by side with their individual km/l and ₹/km numbers. That is your structured baseline, already in a format you can compare against every subsequent tank for the next year.
If you want to understand how CNG vehicles should approach a similar exercise, where km/kg rather than km/l is the unit and dual-fuel switching introduces additional variables, the logic is the same but the numbers look different. The CNG vs petrol rupees-per-kilometre comparison covers that math in detail.
Interpreting What You Find
Three outcomes are possible, and each has a different next step.
Within 1–2%: Your vehicle is likely E20-tuned or E20-compatible and well-maintained. The blend is doing what it should. Carry on tracking quarterly to catch mechanical drift early.
3–6%: Within the measured range for vehicles calibrated on earlier blends. This is a real cost you can now quantify in ₹/km and factor into your monthly budget. Check compatibility via the fuel-lid sticker or owner's manual. If your vehicle is older than an early 2023 build date, budget for possible earlier rubber-seal replacement at your next service interval, the E20 care checklist for older vehicles covers what to ask your service centre.
Above 6%: Something else is likely compounding the E20 effect. Run through the obvious mechanical checklist before blaming the fuel: tyre pressure (check cold), air filter condition, spark plug age, injector cleanliness. A vehicle that was already slightly under-maintained will show a larger E20 impact because the blend demands tighter tolerances. Get a service done, then run the two-tank experiment again and compare.
A mileage drop that appears in your log and persists across multiple tanks is almost always the clearest signal you have that something in the vehicle needs attention. The logic behind using your fuel log as an early-warning system is worth reading if you have not already: when a mileage drop means a service is due walks through how to read that pattern.
Running This as an Ongoing Experiment
Two tanks gives you a baseline. The experiment becomes genuinely useful when you run it continuously. Every fill-up you log is another data point. After two months of Bharometer data you will have a distribution: your best tanks, your worst tanks, and your real central tendency. That distribution is what you compare against your pre-E20 log, or against your numbers from three months ago.
Seasonal variation matters too. August monsoon traffic in Bengaluru or Mumbai adds stop-start time that city-highway mixed numbers do not capture; December is different again. This is why a single two-tank experiment is a starting point, not a conclusion. It gives you a number to anchor to. The months of data after it tell you whether that number is stable, drifting, or recovering after a service.
The national averages published in government and test-agency reports are useful for policy. Your own tank-to-tank log is useful for your fuel budget and your service schedule. Run the experiment, log it properly, and you will know more about your vehicle's real running cost than most vehicle owners in the country.