How BEVDB estimates work

BEVDB Methodology

This page explains how BEV Database turns official WLTP and EPA data into comparable BEVDB estimates, where those estimates are used, and where the model stops. It is the main reference page for "real-world estimate", "BEVDB estimate", and "not official test results" labels across the site.

What The BEVDB Model Calculates

Comparable range estimates

The model estimates how far an EV can go under fixed reference scenarios so different cars can be compared on the same basis.

Scenario-based consumption

It converts official anchor data into scenario consumption and then into scenario range using usable battery energy.

Combined comparison value

It also publishes a single combined estimate for faster shortlist-level comparison across large catalogs.

The BEVDB model is designed for standardized comparison. It is not a trip-specific promise, not a live telemetry feed, and not a guarantee for an individual route.

Inputs And Official Anchors

Usable battery capacity

The model prefers reported usable battery capacity. When that is missing, BEV Database can estimate usable capacity from calibrated nominal-to-usable ratios and mark it as estimated.

Europe: WLTP first

Europe uses WLTP-rated consumption or WLTP range as the main anchor. If only NEDC-era data exists, BEVDB normalizes that input as a fallback instead of treating NEDC as directly equivalent to WLTP.

USA: EPA first

USA uses EPA range and EPA energy-use style inputs as the main anchor. When multiple EPA-style fields exist, the model prefers the most stable battery/range basis and falls back to wall-basis metrics when needed.

Europe vs USA Quick Reference

MarketPrimary official anchorNative public unitReference highway speedDefault combined weighting
EuropeWLTP consumption / WLTP rangekm110 km/h54/46 city-highway, 65/35 mild-cold
USAEPA range / EPA energy-use fieldsmi70 mph55/45 city-highway, 70/30 mild-cold

This matters across the whole site: Europe pages should read as WLTP-plus-km pages, while USA pages should read as EPA-plus-mi pages. Cross-region assets only normalize back to kilometers when a single comparison scale is needed.

Scenario Grid

The public BEVDB range card is built around four fixed reference scenarios. Those scenarios exist to separate speed impact from climate impact without turning the page into a trip planner.

ScenarioReference speedReference temperatureWhat it is for
City (Mild)50 km/h or 30 mph+20 CLower-speed urban use without strong heating penalty
Highway (Mild)110 km/h or 70 mph+20 CSteady higher-speed travel in moderate weather
City (Cold)50 km/h or 30 mph-10 CUrban driving with winter battery and cabin-heat penalty
Highway (Cold)110 km/h or 70 mph-10 CWorst mainstream road-use case on the public card

The model internally uses region-specific anchor logic. For example, the USA combined weighting starts from EPA city/highway weighting, while Europe uses its own empirically stable combined weighting.

How The Combined Estimate Is Built

Combined does not mean one official lab number copied from a source. It is a BEVDB comparison value created from the scenario grid.

City vs highway mix

USA defaults to a 55/45 city-highway weighting that aligns with EPA weighting. Europe defaults to a 54/46 split for the public combined point.

Mild vs cold mix

USA combined range defaults to a 70/30 mild-cold mix. Europe defaults to a 65/35 mild-cold mix.

Consumption and capacity stay aligned

Combined energy use is derived so the displayed combined consumption and combined range remain internally consistent with effective capacity and cold-weather derate.

Official Values vs BEVDB Estimates

Label on siteTypeWhat it means
WLTP range / EPA rangeOfficial source valuePublished regulatory or official-cycle figure
Real Range (est.)BEVDB estimateScenario-based estimate built from official anchors
Combined real range (estimate)BEVDB estimateWeighted aggregation of city/highway and mild/cold outputs
Usable battery (estimated)BEVDB estimateFallback usable-capacity estimate when reported usable kWh is missing
Tool inputsUser inputValues entered or adjusted by the user inside a planner or calculator
Planner defaultsTool assumptionComparison defaults or routing assumptions used by a tool when no direct source row exists
No data / unavailableUnavailableNo defensible public or modeled value is currently published for that field

When a car page says "These figures are not official test results", it refers to the estimate rows above, not to the official WLTP or EPA source rows.

Fallback Rules

  • If reported usable capacity exists, BEVDB uses it. If it does not, BEVDB may estimate usable capacity from nominal battery size plus calibration data and mark that field as estimated.
  • If Europe has WLTP consumption, that is the preferred anchor. If Europe lacks WLTP but has NEDC-era data, BEVDB normalizes that as a fallback rather than treating it as a direct equivalent.
  • If USA lacks the preferred battery-plus-range anchor, BEVDB can fall back to EPA wall-basis metrics such as MPGe or energy-use fields.
  • If the inputs needed for a full scenario grid are missing, a page may fall back to the available official range value or suppress the scenario output instead of inventing a full estimate.

Limits Of The Model

  • It does not model your exact route, elevation, traffic, wind, or charging strategy in real time.
  • It does not know your driving style, tire setup, roof box, payload, or seasonal battery condition.
  • It is built for comparison across many vehicles, so some internal calibration details are intentionally simplified at the public page level.
  • Tool outputs can combine official fields, user overrides, and BEVDB estimated anchors. When that happens, the UI labels the active source instead of pretending everything is equally official.

Where This Methodology Is Used

Car pages

Real Range (est.), combined estimate language, and estimate disclaimers on car pages point back to this methodology page.

Europe tools

The Europe Road Planner and Europe Money Economy pages use the WLTP-plus-km side of the estimate layer and should reference this page for scenario assumptions and source boundaries.

USA tools

The USA Road Planner and USA Money Economy pages use the EPA-plus-mi side of the same methodology, with region-specific anchors rather than a Europe-first shortcut.

Research reports

Data-led assets such as the real-world EV range report link back here as the canonical explanation of the estimate layer.

Versioning And Changelog

Current public range-model version: v13.6

  • Uses separate WLTP and EPA anchor logic rather than one blended global shortcut.
  • Publishes a consistent 2 x 2 scenario grid plus a weighted combined estimate.
  • Marks usable-capacity fallbacks and keeps estimate labels separate from official source values.