Matthias SpeicherShowcase
E-truck database
A curated database of electric trucks: real consumption figures, ranges, field reports. It started as a precondition for the fleet calculator, but it stands on its own.
The reason sits in the head of the user. Confronting someone with abstract numbers, kWh, efficiencies, consumption curves, is enormously hard, the figures stay foreign. With real models they may already have seen at the dealer, in a brochure or online, and that they are interested in, they can identify far more easily. Only the real vehicle makes the calculation tangible. That is the database’s actual function for the calculator, and at the same time it is usable on its own, by anyone looking for real figures rather than lab values.
Schema 0.3, as of 04.2026. 28 models, 6 OEMs. ccs_kw 28 of 28, battery capacity 24 of 28, mcs_kw 8 of 28. A source per entry. Values I cannot evidence stay null and get flagged.
Where you can see how I think
Three decisions that shape the database, each with the price it cost.
A source per entry
Every value has an origin: manufacturer figure, field report, my own measurement. That costs maintenance, but without an origin a number in this field is worthless, because the entire point of the database is being more reliable than the lab values.
Values I cannot evidence stay null, not estimated
Where I have no solid value, the entry is null, not an estimate. That is uncomfortable, because an estimated number would look more complete. But an estimated number that looks like a measured one is exactly the kind of quiet dishonesty the database was built against in the first place. Better a gap you can see than a number you cannot trust.
Three generic trucks for the easy way in
The guided mode of the calculator cannot carry a choice between 28 models, that overwhelms anyone who has not dealt with the topic yet. So I derived three generic trucks from the 28 real ones, covering the typical classes. Anyone who wants to go deeper reaches for the full database, anyone who just wants a feel starts with the three. The same data, two resolutions, depending on how far along the user is.
Every value with an origin
The schema sits in the same file as the data, so field descriptions and content cannot drift apart.
Interface and field descriptions shown in German.
The database inside the fleet calculator
The actual point: instead of abstract kilowatt-hours you pick a vehicle you already know.
