Demo Motors Lumen Electric
2026 model year, Netherlands
- Powertrain
- Battery electric
- Measured under
- WLTP
- Energy use
- 16.0 kWh/100 km
- Range
- 400 km
- List price
- €40,000
- Record completeness
- 100%
The price is the smallest part of what a car costs.
DriveMetrio adds up purchase, depreciation, energy, maintenance, insurance and tax across three, five or ten years, for the Netherlands and the United States, and shows you where each number came from.
The tools work on figures you supply, and the catalogue now carries real specifications from public open data. What is still missing is prices and tax rates: those defaults are placeholders, and every page that uses one says so.
What goes into the figure
Eight lines, each with a unit and an origin.
- Purchase price
- amount
- Residual value at the end of the term
- share of purchase price
- Financing, if any
- rate and term
- Energy use
- kWh or litres per 100 km
- Energy price
- per kWh or per litre
- Charging loss
- share of energy drawn
- Maintenance and insurance
- per year
- Tax, registration and fees
- per year and one-off
- Marker
- You enter it
- Marker
- Documented default
- Marker
- Cited dataset
Financing principal never gets added on top of depreciation. Both describe the same money leaving your hands, and counting them twice is the most common way a cost-of-ownership figure goes wrong.
Three commitments that decide how everything else is built
Every number names its source
A figure on a DriveMetrio page is one of three things: a value you entered, a default we have written down and dated, or a measurement we took from a dataset and cited. There is no fourth category, and nothing is estimated into a gap.
One method, two markets
The Netherlands and the United States get the same calculation, their own currency, their own units and their own tax treatment. A WLTP consumption figure and an EPA one are never averaged, converted silently, or stored in the same column.
A result you can reproduce
Assumptions are dated rather than overwritten, and imports record which version of our normalisation produced them. A figure you saw last month can be worked out again, with the inputs it actually had.
A catalogue record, as it will look
The standard that measured a figure sits next to the figure. A field with nothing in it reads as missing, not as zero. Patchy records are the normal case in open vehicle data, and the catalogue has to show them honestly.
Demo data. Fictional vehicles and placeholder prices, included so the interface has something to show. Not a real comparison.
Fixture Automobiles Halcyon Plug-in
2025 model year, Netherlands
- Powertrain
- Plug-in hybrid
- Measured under
- Standard not recorded
- Energy use
- —
- Range
- —
- List price
- —
- Record completeness
- 30%
Where the build has got to
Working now
- The cost calculator, with every assumption listed on the page
- The electric-against-petrol comparison
- The vehicle catalogue, with search and filtering
- Vehicle specifications from public open data, with provenance per figure
- The published methodology behind every formula
Not yet
- Real prices and tax rates, in place of placeholder defaults
- Researched residual values, the biggest cost in any result
- Wider coverage: the catalogue is a sample of each market, not all of it