EV kWh per 100 miles calculator
30 kWh used over 150 miles is 20 kWh per 100 miles and 12.4274 kWh per 100 km: the sticker-style labels worked out from the energy and distance you actually measured on a trip. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Energy kwh
- 30
- Distance
- 150
- Distance unit
- Mi
- Distance mi
- 150
- Distance km
- 241.4016
- Kwh per 100mi
- 20
- Kwh per 100km
- 12.4274
This EV kWh per 100 miles calculator converts the energy your electric vehicle actually used over a measured trip into the standard efficiency labels used on stickers, dashboards, and fleet reports: kilowatt-hours per one hundred miles and kilowatt-hours per one hundred kilometers. Enter energy in kilowatt-hours, distance in miles or kilometers, and the engine returns kWh per 100 mi, kWh per 100 km, watt-hours per mile and per kilometer, plus the reciprocal figures miles per kilowatt-hour and kilometers per kilowatt-hour. The arithmetic is fully deterministic: efficiency equals energy divided by distance, scaled to a hundred-unit basis, with the exact international mile of 1.609344 kilometers for dual-unit reporting.
What kWh per 100 miles tells you
Kilowatt-hours per one hundred miles (and the metric twin kilowatt-hours per one hundred kilometers) answer a simple operational question: how much battery energy the car spent for each hundred units of road. Drivers compare sticker ratings after a highway loop; fleet managers normalize routes of different length; journalists and reviewers quote the same label so two cars can be ranked on equal footing.
This calculator does not invent efficiency from weather, elevation, cabin heat, or speed profiles; it trusts the energy and distance you measured and applies the closed-form identities kWh per 100 mi equals energy in kilowatt-hours divided by distance in miles times one hundred, and kWh per 100 km equals energy divided by distance in kilometers times one hundred.
If you already have an efficiency figure in one unit and only need to convert it to another, use a dedicated unit converter; this page stays focused on computing the label from raw trip energy and measured distance so worksheets, APIs, and browser demos share one stable contract.
Where measured-trip efficiency checks fit in planning, fleets, and software
Road testers and owners meet this calculation when the charge app shows thirty kilowatt-hours used and the trip computer shows one hundred fifty miles, and the only remaining step is the sticker-style label that peers and listings expect. Fleet operators batch the same formula across vehicles and shifts to flag routes that burn more energy per hundred miles than the fleet budget allows, or to compare winter versus summer legs without rewriting unit math in every spreadsheet.
Travel and mobility products call the contract from scripts when a user ends a navigation session and the app should show real-world consumption next to the manufacturer rating. Students and driving instructors use it to connect the textbook idea of energy per distance with a concrete number from a weekend journey, including classic metric examples such as twenty-four kilowatt-hours over two hundred kilometers yielding twelve kilowatt-hours per one hundred kilometers.
Product and education tools use the dual mile and kilometer outputs when audiences mix US customary and metric units in the same classroom or marketplace. Pair it with range or trip-cost helpers when you already know efficiency and need distance or money, and keep this tool for the moment you have measured energy and distance and need the standard hundred-unit efficiency label.
What you can do with it
Post-trip efficiency label
Turn charge-session kWh and odometer or GPS miles into kWh/100mi and kWh/100km for reviews, listings, and personal logs.
Fleet route normalization
Batch energy and distance across shifts to compare routes and seasons on a common hundred-mile or hundred-kilometer basis.
FAQ
What does the EV kWh per 100 miles calculator cost?
It is free in your browser on this page.
What happens if energy or distance is zero or negative?
Zero or negative energy or distance cannot define a meaningful consumption rate.
Can I enter distance in kilometers?
The response still reports both kWh/100mi and kWh/100km plus reciprocal efficiencies.
Does this convert an existing efficiency figure between units?
No. This tool computes efficiency from measured energy and distance. To convert an already-known Wh/mi, mi/kWh, or kWh/100km value, use an EV efficiency unit converter.
Where do I find the energy and distance for a trip?
Take the kilowatt-hours drawn from the battery over the leg from your car's charge app or trip screen, and the distance from the odometer or GPS for that same leg. Both figures must cover exactly the same stretch of road.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/travel/ev-kwh-per-100mi \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"energy_kwh":30,"distance":150}'const res = await fetch("https://api.kit.forhosting.com/travel/ev-kwh-per-100mi", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"energy_kwh": 30,
"distance": 150
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/travel/ev-kwh-per-100mi",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"energy_kwh": 30,
"distance": 150
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/travel/ev-kwh-per-100mi", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"energy_kwh":30,"distance":150}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"energy_kwh":30,"distance":150}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/travel/ev-kwh-per-100mi", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"energy_kwh": 30,
"distance": 150
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "travel.ev_kwh_per_100mi",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Zero or negative energy or distance is rejected with invalid_input because a non-positive trip cannot define a consumption rate.
What kWh per 100 miles means and what the response contains
The response echoes energy_kwh, the input distance and distance_unit, normalized distance_mi and distance_km, kwh_per_100mi and kwh_per_100km, the companion rates wh_per_mi and wh_per_km, the reciprocal efficiencies mi_per_kwh and km_per_kwh, the precision used, a method tag ev_kwh_per_100, and a compact formula string for audits. There is no Monte Carlo path and no live traffic or temperature feed: the engine either builds a finite positive efficiency inside the supported numeric range or rejects the input with invalid_input. Rejected cases include missing energy or distance, non-finite values, magnitudes above the supported ceiling, and any energy or distance that is zero or negative, because dividing by zero distance or scaling with a non-positive energy burn is not a valid efficiency label.
How energy, distance, and units are read and stay consistent
Optional leading plus signs and scientific notation on numeric strings are allowed when they parse as finite decimals; embedded spaces, hex prefixes, and non-numeric tokens are rejected with a clear message so a bad cell does not become a wrong efficiency claim. The preferred fields are energy_kwh for the kilowatt-hours drawn from the pack over the leg and distance for the odometer or GPS length of that leg, but aliases such as energy, kwh, energy_used, consumed_kwh, dist, trip_distance, miles, and km are accepted so spreadsheets, query strings, and typed forms can reuse the same contract. distance_unit selects whether distance is interpreted in miles (mi, the default, matching the kWh-per-100-miles search intent) or kilometers (km); case-insensitive aliases such as mile, miles, kilometer, and kilometres are accepted. After validation the engine normalizes both distance_mi and distance_km using the exact international mile constant, computes kWh per 100 mi and per 100 km, and derives Wh per mile, Wh per kilometer, miles per kWh, and kilometers per kWh so dual-unit readers do not re-convert by hand. An optional precision field, with aliases decimals and dp, chooses how many decimal places to expose, defaulting to four and capped at fifteen so JSON goldens stay stable across runtimes. Pair the free browser run on this page with the priced API when you need the identical mathematical result inside an automated pipeline without re-implementing Wh and kWh scaling yourself.
Where measured-trip efficiency checks fit in planning, fleets, and software
On this page the work runs entirely in your browser; through the API each successful lookup costs $0.002, failed validation is not charged, and nothing is stored after the response returns. That split — free interactive exploration and a priced, identical API — matches the rest of the KIT tier-A catalog and lets you move from a dashboard demo to an automated pipeline without changing the mathematical result.
Integration use cases
App and CI fixtures
Call the API for reproducible efficiency numbers in mobility apps and tests without re-implementing mile–kilometer scaling.
Technical questions
How is kWh per 100 miles calculated?
kWh per 100 mi = (energy_kWh ÷ distance_mi) × 100. kWh per 100 km = (energy_kWh ÷ distance_km) × 100, using the exact international mile 1.609344 km when converting units.