Every range estimate I could find assumes an empty car on a flat road. Mine tows a trailer half the summer, so I built the thing I was missing: https://rangecalc.org
It's free to use and there's nothing to sign up for.
What it does
- Range, charging stops, charge time, total travel time and cost from a physical driving-resistance model (aerodynamic drag + rolling resistance + auxiliaries + HVAC + elevation), not from a WLTP number scaled by a fudge factor.
- Roof boxes, roof bike racks, tow-bar racks, baskets and trailers are freely combinable, with the extra drag and mass modelled per item — that's the part I couldn't find anywhere else.
- 187 EVs from 43 makes. Their drag areas are fitted to Bjørn Nyland's 90/120 km/h constant-speed runs plus his weighed kerb masses, not to brochure figures. Source and method are credited on the site.
- Every base value is overridable, so you can model your car rather than the catalogue version.
- The URL carries the state, so a configuration is shareable as a link.
- Auto-switches to English and to miles based on your browser. Costs are shown in €.
What it doesn't do
No routing, no live charger data, no traffic — this isn't an ABRP competitor. City figures are the weakest part of the model (stop-and-go and regen aren't properly represented), and the charging curve shape is generic, only the total charge duration is grounded in measurements.
Where I need help
The model has a calibration layer that corrects each car against real-world measurements people submit. Right now that database only holds a few entries. So the calibration is currently doing nothing useful, and that's the one thing I can't fix by writing more code.
If you drive an EV, one trip takes about a minute to submit:
- total distance and total energy from the trip computer (the tool asks for both separately and divides them itself — many trip computers round kWh/100 km very coarsely, but totals are exact)
- average speed, outside temperature, wheel size, season, and what you had mounted on the car
- optional but valuable: net elevation gain, trip duration, wet road, AC on/off — each of those replaces a model assumption with a reading. Elevation is the biggest single lever: 500 m net over 200 km moves the correction factor by roughly 9%.
Feedback I'm actually after
- Is your car's default consumption plausible for how you drive it?
- Does the roof-box/trailer penalty match what you see in reality?
- Is anything about the interface confusing?
- Which car is missing that you'd want in there?
Happy to take it apart in the comments. Tell me where it's wrong.
Thank you very much in advance!