Skip to content
Adaptr
← Battery passport software

Worked example · Reviewed 30 September 2026

What a battery passport actually looks like.

Below is a complete passport for a demonstration battery: what it reported over three years, what went wrong twice, what its maker declared, and what a member of the public does not see. It is the same layout a real scanned code reaches.

Sample dataAdaptr Demo Battery — not a real battery, not a real operator, and not a compliance record. Every figure below is illustrative.

Adaptr Demo Battery — sample data

LiFePO₄ storage module, 48 V · demonstration operator · put into service 11 March 2023

DEMO-1042 · UPI 8f24-c1a7-4b90-2d55

Reporting normally. Health has fallen from 100% to 91% over three years, which is ordinary for its age and use.

Last reading 30 Sep 2026, 14:02 · 1,118 days of records

What has been observed

Measured from the battery’s own management system. These are readings, not a certification — and where the record has a gap, the gap is shown rather than drawn over.

State of health today91%
Full charge cycles counted842
Widest cell spread seen84 mV
Temperature range seen4 °C – 38 °C
Faults recorded2
Longest gap in reporting6 hours

What happened to it

Every fault the battery reported, kept whether or not it was resolved. A record that dropped the resolved ones would be a record that flatters the pack.

  • Over-temperature warning, cleared after 40 minutes.
  • Cell imbalance above the pack’s threshold, cleared after balancing.
  • Six hours of silence — no readings received. Cause not recorded.

What the maker declared

Supplied by the manufacturer and inherited by every pack of this model. Adaptr has not verified these figures, and says so rather than presenting them beside the measured ones without distinction.

ChemistryLiFePO₄
Rated capacity100 Ah
Rated energy4.8 kWh
Nominal voltage48 V
Expected lifetime4,000 cycles
Carbon footprint680 kg CO₂e
Recycled contentcobalt 12% · lithium 4%

Not shown here

Where this battery is installed, who operates it, the economic operator’s registered identifier, and the reading-by-reading record are not public. Authorised parties — the operator, a recycler taking the pack on, or a regulator — can be granted access to the full record. The regulation specifies different information for different audiences, which is why one code has to serve several.

Why two audiences, one code

The record above is what anyone scanning the code would see. The operator sees the reading-by-reading history; a recycler taking the pack on can be granted what they need to assess it; an authority can be given the registered identifier that is deliberately absent from the public view.

That split is a requirement rather than a product choice — see what the QR code must resolve to.

Source: Regulation (EU) 2023/1542, consolidated text

How a real one differs

A real passport is reached from the code on the battery, not from a page like this one — individual passports are deliberately kept out of search results, because a record about one asset is not editorial content and a fleet of them is not a website.

Its figures also come from the pack rather than from this page. Which fields arrive, and how often, depends on the hardware and the integration; the honest first step is to look at what yours reports.

From 18 Feb 2027 the record behind the code is what is required. See what a passport must contain and what the deadline requires.

A practical first step

See this for one of your own batteries.

Bring a pack and what your hardware reports about it. We will show you the record it would produce, and what a passport would still be missing.

Request a demo