TR-MRV-Bench v0 · 59 facilities · 4 CBAM scopes

The bench. Every facility, every source.

Every row below cites a public, traceable source. Disclosure rows have audit-grade Scope 1 from operator integrated reports / TSRS filings / ISO 14064-1 verifications. Climate TRACE rows pull from the CT v6 per-asset details endpoint. cf-corrected rows are formula-only: capacity × route-EF × cf. Sort by clicking a column header.

01 Map

02 Filter

Company / plant Scope City Capacity (t/yr) Label tCO₂ Provenance Assurance cf-corrected formula (LOPO) Ratio EU default Source · notes

Each company/plant link goes to a deep-linkable per-facility page with full evidence (audit-grade Scope 1, source PDF, conformal CI, EnMAP scene index, Beirle NOx cross-check where available) plus a printable single-page audit summary for verifiers.

Provenance: direct = operator-published per-plant figure; allocated = our split from operator-published group total using disclosed production / capacity share; derived = back-computed; disputed = flagged (excluded from leave-one-plant-out test set). Assurance: iso14064 = ISO 14064-1 third-party verified; tsrs_assured = TSRS-compliant limited assurance (KGK-registered audit firm); operator_audited = published in Big4-audited annual report without GHG-specific verification. cf-corrected formula (LOPO) = capacity × route-EF × cf, evaluated leave-one-plant-out (each plant's route emission-factor derived only from the other audit-grade plants). This is the headline result: +82.3% log-MAE reduction vs the EU default across the 19 validatable plants. Two single-plant routes (N₂O-controlled and blender fertilizer) can't be validated this way and show "not validatable." An optional in-browser demo net (iz, at /verify/) does not beat this formula. Ratio = formula ÷ truth.

06 Claim or correct a facility

If you operate or audit a facility on this bench and have a more recent or more accurate Scope 1 disclosure than what's shown, submit it here. Submissions open a pre-filled GitHub issue you can review before posting — no GitHub account is required to fill the form, but you'll need one (or send the same payload by email) to actually submit.

Corrections that include a verifiable public source land within 24 hours. Apache-2.0 means anyone (including the operators themselves) can fork and host their own bench.