EV range at highway speed calculator

Zero or negative capacity or consumption is rejected with invalid_input.

Why highway speed shortens EV range and what this tool returns

The response echoes capacity_kwh, usable_pct, usable_kwh, highway_consumption, consumption_unit, range_km, range_mi, precision, a method tag ev_range_at_speed, and a compact formula string. When you also provide rated_consumption in the same unit, the response adds rated_range_km, rated_range_mi, range_reduction_pct, and range_ratio so you can show how much shorter the highway leg is versus the sticker cycle. Optional speed_kmh is echoed for display only and does not alter the energy math; the consumption figure already encodes the speed effect. Rejected inputs include missing capacity or highway consumption, non-finite values, non-positive pack capacity, usable_pct outside zero to one hundred, and zero or negative consumption rates, because those cases do not define a meaningful trip distance.

How capacity, highway consumption, and optional rated rates are read

The preferred fields are capacity_kwh for the nominal pack size in kilowatt-hours and highway_consumption for the energy rate at sustained highway speed, but aliases such as capacity, battery_kwh, pack_kwh, consumption, highway_rate, and energy_rate are accepted so spreadsheets and forms can reuse the same contract. consumption_unit selects the interpretation: kwh_per_100km is the default metric consumption rate familiar from European stickers and trip computers, while wh_per_km and wh_per_mi match dashboard-style watt-hour rates. usable_pct defaults to one hundred when omitted and may be set from zero to one hundred to model a manufacturer usable window, a software buffer, or a partial charge before departure. rated_consumption is optional; when present and positive it must use the same unit as highway_consumption and enables the reduction comparison. speed_kmh is optional documentation of the cruise speed you have in mind and is never used to invent a consumption curve. Optional leading plus signs and scientific notation on numeric strings are allowed when they parse as finite decimals; non-numeric tokens fail with a clear invalid_input message. After validation the engine computes usable_kwh, applies the matching closed-form range formula for the selected unit, always reports both kilometers and miles using the exact international mile constant, and optionally computes range_reduction_pct as one hundred times the difference between rated and highway range divided by rated range. 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.

Where highway-range estimates fit in trips, fleets, and product UX

Buyers comparing two cars can hold capacity fixed and swap highway_consumption values to see which platform keeps more distance at cruise. Students and driving instructors use the optional rated_consumption field to connect the textbook idea of mixed-cycle efficiency with the harsher real-world freeway burn rate. 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.