EPD-Norge - EPD-Norge (EPD Global)

Norway's register of verified Environmental Product Declarations, run by the Norwegian EPD Foundation (EPD-Norge): the climate impact of construction products, building services, furniture and electrical equipment, per life cycle module.

Non-profit

EPD
Construction

SpecialistRestricted licence

Publisher's page Browse 120,905 factors

Factors

120,905

Values

120,942

One per year and method

Countries

59 regions, sub-national included

Edition

EPD_NORGE_2026-10-02

published 2 Oct 2026 · all versions

Last loaded

5 Oct 2026

Report a newer version

Overview

EPD-Norge (Næringslivets Stiftelse for Miljødeklarasjoner) is the Norwegian programme operator for EPDs. Manufacturers from Norway and abroad publish third-party verified EPDs under its rules, from ready-mixed and precast concrete to cables, switchgear, office furniture and building boards. The programme's site is epd-norge.no.

Its digital datasets are published through EPD-Global Digi in the ILCD+EPD format, on the soda4LCA node epdnorway.lca-data.com, the same format and interface ÖKOBAUDAT uses.

At a glance

Publisher: EPD-Norge (EPD Global)
Kind: Non-profit
Scope: Specialist
Home region: Norway
Edition: EPD_NORGE_2026-10-02
Licence: Restricted licence (epd-norge-digi-terms)

Open data

How this works

What open-climate.ai standardised

over the publisher's own fileHow we standardise

One category axis

120,905 of 120,905 factor values mapped to one category

88,969 keep the publisher's own classification too

Learn more 6 checks behind this

Coded regions

59 regions as ISO or registry codes

1,369 take the publisher's default region, stated rather than assumed

Learn more 3 checks behind this

Canonical units

6 canonical units in 6 unit families, raw unit kept

Learn more 4 checks behind this

Warming potentials

None is converted: every value keeps the publisher's GWP.

120,905 factor values left on the publisher's GWP

Learn more 7 checks behind this

8 more things standardised

Declared boundaries

22 boundary codes

30,589 factor values state in, out or varies for each scope term

Learn more 7 checks behind this · 1 known limitation

Parts and parents

108,211 factor values grouped under 12,694 parents

Use a part on its own, or the parent when you want the whole.

Learn more 3 checks behind this

Summed totals

30,411 totals summed from their printed parts

Learn more 3 checks behind this · 1 failed

Data quality

120,905 of 120,905 factor values rated on one quality tier

Learn more 7 checks behind this · 1 known limitation

EPDs and suppliers

120,637 EPDs

119,649 factor values naming a supplier

Learn more 1 check behind this · 1 known limitation

Languages

English: 100.0% of factor values

Danish: 4.2% of factor values

German: 0.1% of factor values

Spanish: 0.1% of factor values

French: 0.2% of factor values

Italian: 0.0% of factor values

Norwegian: 13.2% of factor values

Portuguese: 0.1% of factor values

Swedish: 1.0% of factor values

Learn more 11 checks behind this · 1 known limitation

Traceable to the source

12,998 source rows archived

95 rows skipped, each with a reason

Learn more 4 checks behind this · 1 failed

Stable addresses

Slugs never break

Learn more

Audit checks

107 passed10 known limitations2 failed3 enforced when loadedlast run 5 Oct 2026

Checks we run on every load to keep the data above trustworthy. Counts are for this library; the grey figure is the same check across all libraries. Point at the i to see why a check matters.

What the statuses mean How checks are counted Why we check How checks are grouped

Needs attention

Summed totals equal their parts on every gas
Failed · 1 in this library
Why it matters Where a total is the sum of its parts, the two must agree on every gas. Otherwise your footprint changes depending on whether you use the total or the parts.
No duplicate factors are served
Failed · 174 in this library · 174 in all libraries
Why it matters Identical duplicates split search results and invite counting the same factor twice.
Separate stages of one activity are linked as parts
Known limitation · 27 in this library
Why it matters Stages served as unrelated factors give no total, so you may use one stage and miss the others.
No default value is withheld for poor quality
Known limitation · 993 in this library
Why it matters A default rated too poor to serve is hidden from search and exports, so that factor is missing for you even when it is the right one.
A supplier named in the source is linked to the factor
Known limitation · 724 in this library
Why it matters If the supplier is named but not linked, you cannot filter by supplier or tell a company's own figure from a generic one.
Factors are searched on their English name where one exists
Known limitation · 1 in this library · 20 in all libraries
Why it matters Search matches your query against one name per factor. A name kept in the publisher's language, when an English one exists, is harder to find in English.
No factor value claims two things that cannot both be true
Known limitation · 2 in this library · 3,243 in all libraries
Why it matters For example, a purchaser price that leaves out retail or delivery, or packaging on an energy unit. One of the two claims is wrong, and you cannot tell which.
No factor value the publisher has withdrawn is still served
Known limitation · 6,622 in this library · 10,480 in all libraries
Why it matters The publisher's end date for the value has passed. The figure may be out of date, so look for a newer one before you use it.
One activity keeps one family across its units
Known limitation · 1 in this library · 9 in all libraries
Why it matters When a publisher prints the same activity per kg and per kWh, the two factors belong to one activity family, with the unit as a choice. Filed as separate activities, they look unrelated, and nothing says they measure the same thing.
No factor description is too long to display in full
Known limitation · 3 in this library · 28 in all libraries
Why it matters Text beyond the limit is cut short on the factor page, so part of what the publisher wrote shows only in the download.
Every categorised factor has a GHG Protocol scope
Known limitation · 1 in this library · 30 in all libraries
Why it matters Without a scope, you cannot tell whether the factor belongs in Scope 1, 2 or 3 of your inventory, and you have to place it yourself.
No factor answers a question that does not arise for it
Known limitation · 1 in this library · 5 in all libraries
Why it matters Some questions only make sense for some kinds of factor. An answer where the question should not arise is either misplaced, or a sign the kind is too coarse for that factor, so each case is reviewed.

One category axis

Learn more

Every source category maps to our vocabulary
Enforced when loaded
Why it matters A factor with no category drops out of every category filter and comparison. The load stops rather than serve one.
The publisher's classification is kept
Passed
Why it matters You can still find a factor the way the publisher filed it, and check our mapping against theirs.
Every classification level has a valid parent
Passed
Why it matters A broken tree hides factors from browse and puts them in the wrong category totals.
Every product code comes with the codes above it
Passed
Why it matters In product codes like HS or CPC, a search for a chapter should reach every code inside it. A missing level hides the factor from that search.
A publisher's own classification is used only by that publisher
Passed
Why it matters A publisher's own tree only makes sense inside its library. Filed under another publisher's codes, a factor would show up in categories that do not describe it.
A standard classification code has one label in every library
Passed
Why it matters Codes like NACE or NAICS are meant to link libraries. If one code carries two labels, you cannot tell whether both libraries mean the same activity.

Coded regions

Learn more

Every region is a known code
Enforced when loaded
Why it matters Free text like “France continentale” cannot be filtered or joined to your own data. A code can.
No named region is filed under a broader one
Passed
Why it matters A French factor filed as World would be applied to the wrong country, or lose to a global value in a search for France.
Every region sits in the world hierarchy
Passed
Why it matters A search for Europe has to reach France. A region outside the hierarchy is invisible to broader searches.

Canonical units

Learn more

Every unit is a known code
Enforced when loaded
Why it matters Activity data only multiplies correctly when the unit is exact. An unknown unit stops the load.
One source unit maps to one unit
Passed
Why it matters If one of the publisher's units were read as two different units, factors that share it would give inconsistent footprints.
A unit label means the same in every library
Passed
Why it matters Comparing two libraries is only safe when a label like t.km means tonne-kilometre in both.
A unit label that names no basis folds one way
Passed · 1 in all libraries
Why it matters A label like GJ says nothing about the heating value behind it. If the same bare label folds to two different units, two factors that look alike are not comparable.

Declared boundaries

Learn more

Every boundary states what it includes
Passed
Why it matters Cradle-to-gate and full life-cycle values can differ several times over. Without a stated boundary you cannot tell which you are adding up.
Boundary scope terms are known codes
Passed
Why it matters Consistent terms let you keep exactly the life-cycle stages your inventory needs.
No two factors for the same activity partly overlap in scope
Passed
Why it matters Two totals that share some stages but not all cannot safely be added or swapped: adding them counts the shared stages twice.
Separate stages of one activity are linked as parts
Known limitation · 27 in this library
Why it matters Stages served as unrelated factors give no total, so you may use one stage and miss the others.
Every part of a factor states its boundary
Passed
Why it matters A part with an unknown boundary cannot be told apart from the other parts, so you cannot pick out, say, the combustion share of a total.
Every biofuel counted with its biogenic CO2 says how much
Passed
Why it matters Some publishers count the CO2 a burnt biofuel releases and others leave it out. Search tells the counting ones apart by their biogenic CO2 figure, so a factor without it would be offered to someone who asked to leave that CO2 out.
No recycling credit is hidden inside a life-cycle total
Passed
Why it matters A negative total may be a credit for avoided emissions. Filed as a life-cycle burden, it would quietly subtract emissions from your footprint.

Warming potentials

Learn more

Methane and nitrous oxide figures match the stated GWP
Passed
Why it matters If a gas's CO2e is not its mass times the stated GWP, the GWP label is wrong, and converting the value to another GWP version would give a wrong result.
Every convertible value has its AR6 version
Passed
Why it matters Reporting now asks for AR6. Mixing AR5 and AR6 shifts methane-heavy totals by several percent.
CO2e totals leave out what their basis excludes
Passed
Why it matters A value's basis names the carbon pools its total leaves out. When the gas breakdown shows the total counting one of them anyway (biogenic CO2, land-use change, or biogenic methane on a fossil-only value), the label or the total is wrong.
Values that exclude a carbon pool list the gases behind the total
Passed · 50,262 in all libraries
Why it matters With no breakdown by gas, nothing can confirm that a fossil-only or biogenic-CO2-excluded total really leaves those pools out. The value rests on the publisher's word alone.
Standardised figures keep every gas the publisher lists
Passed
Why it matters The comparable figure we serve must carry each gas the publisher reported. A lost gas makes the breakdown disagree with the total and hides that gas from you.
Every value states what its CO2e total includes
Passed
Why it matters For a biofuel, a total with or without biogenic CO2 can differ widely. Without that convention you cannot tell which one you are comparing.
A library with no AR6 version at all has a recorded reason
Passed · 2 in all libraries
Why it matters Values that cannot be converted to AR6 cannot be compared with AR6 figures. That has to be a documented decision, not something missed at load.

Parts and parents

Learn more

Every part links to a valid parent
Passed
Why it matters A part that points nowhere gets summed twice or dropped when you use the parent total.
No factor is an unlinked part of another factor
Passed
Why it matters If one stage of a total is also served on its own, beside that total, adding both counts the same emissions twice.
Every factor points to its top parent
Passed · 1 in all libraries
Why it matters Search groups parts under their top factor. A stale link shows a part as a stand-alone result.

Summed totals

Learn more

Summed totals equal their parts on every gas
Failed · 1 in this library
Why it matters Where a total is the sum of its parts, the two must agree on every gas. Otherwise your footprint changes depending on whether you use the total or the parts.
Every summed total has a classification when its parts do
Passed
Why it matters A total with no classification drops out of every category filter, even though its parts are filed there.
Summed totals keep their parts' classification
Passed
Why it matters A total takes a classification only when all its parts share it. Otherwise it lands in a category its parts do not support, or misses one they all share.

Data quality

Learn more

Quality ratings fall inside their scale
Passed
Why it matters An out-of-scale rating cannot be compared, so the value would be ranked arbitrarily.
Every zero value is explained
Passed
Why it matters A zero can be real (contracted renewable power) or a gap in the data. A gap read as real erases emissions from your total.
No default value is withheld for poor quality
Known limitation · 993 in this library
Why it matters A default rated too poor to serve is hidden from search and exports, so that factor is missing for you even when it is the right one.
No implausibly high per-kilogram value is rated reliable
Passed
Why it matters Above 1,000 kgCO2e per kg is often a unit slip, such as grams read as kilograms. Rated reliable, such a value could inflate a footprint a thousandfold.
Every quality level gives a recognised reason
Passed
Why it matters The reason explains why a value got its quality level. An unrecognised one cannot be filtered on or explained to you.
A zero that is only a gap in the source is withheld
Passed
Why it matters A zero with no quality signal, or an implausible regulatory default of zero, is more likely missing data than a real zero. Served, it would erase emissions from your total.
The library is not rated entirely on one fallback quality level
Passed
Why it matters When every value gets the same level because the publisher gives no quality signal, the level tells you nothing and cannot rank one value above another.

EPDs and suppliers

Learn more

A supplier named in the source is linked to the factor
Known limitation · 724 in this library
Why it matters If the supplier is named but not linked, you cannot filter by supplier or tell a company's own figure from a generic one.

Languages

Learn more

Every factor has an English name
Passed
Why it matters Every factor can be searched and cited in one shared language, whatever the publisher's.
Translations match the current source text
Passed · 310 in all libraries
Why it matters When the publisher rewords a label, an old translation can describe a different activity than the one priced.
Translations follow a corrected source text
Passed · 4 in all libraries
Why it matters When we correct an English label, a French or German label translated from the old wording can still describe what the old wording said.
Recorded translations survive a reload
Passed · 5 in all libraries
Why it matters A reload rewrites a library's labels; a translation we recorded and did not put back leaves that factor without a label in that language.
Every served factor has a name
Passed
Why it matters A factor with no name in any language shows as a blank row: you cannot search for it or tell what it measures.
Factors are searched on their English name where one exists
Known limitation · 1 in this library · 20 in all libraries
Why it matters Search matches your query against one name per factor. A name kept in the publisher's language, when an English one exists, is harder to find in English.
Every language with a main name also has a full name
Passed
Why it matters Without the full name, the detail that tells similar factors apart is missing in that language, so two different factors can look identical.
Full names are built from their parts in the same language
Passed
Why it matters A full name must read as the main name followed by its detail. Translated separately, it can drift and describe a slightly different activity.
Every text is labelled with its real language
Passed
Why it matters A French name labelled English would be shown to English readers and matched against English searches.
Every description is available for display and translation
Passed
Why it matters A description missing from the per-language text store is not shown in your language, and never gets translated.
Every usage note is available for display and translation
Passed
Why it matters Names and notes are served from one text store per language. A note missing from that store is not shown, and never gets translated.

Traceable to the source

Learn more

Values traced to one source row agree with each other
Passed
Why it matters Each value traces back to one source row. When values that disagree share a row, it can back only one of them, which weakens that audit trail.
No duplicate factors are served
Failed · 174 in this library · 174 in all libraries
Why it matters Identical duplicates split search results and invite counting the same factor twice.
No factor value claims two things that cannot both be true
Known limitation · 2 in this library · 3,243 in all libraries
Why it matters For example, a purchaser price that leaves out retail or delivery, or packaging on an energy unit. One of the two claims is wrong, and you cannot tell which.
No factor value the publisher has withdrawn is still served
Known limitation · 6,622 in this library · 10,480 in all libraries
Why it matters The publisher's end date for the value has passed. The figure may be out of date, so look for a newer one before you use it.

Other checks

One activity keeps one family across its units
Known limitation · 1 in this library · 9 in all libraries
Why it matters When a publisher prints the same activity per kg and per kWh, the two factors belong to one activity family, with the unit as a choice. Filed as separate activities, they look unrelated, and nothing says they measure the same thing.
An activity's grouping key names only the activity
Passed · 5 in all libraries
Why it matters If the key also carried the unit, country or scope, one activity would split into several, and search would not show you its other versions side by side.
A Creative Commons credit names its licence
Passed
Why it matters CC BY asks you to say which licence applies. A credit that leaves it out makes your attribution incomplete when you copy it.
No note of ours appears in the credit or licence notice
Passed
Why it matters Our own notes on how we handle the data would end up in the credit you reproduce, as if the publisher had written them.
The credit line carries no terms of use
Passed
Why it matters You copy the credit line as it stands. Terms of use belong in the licence notice, which you read rather than reproduce.
Every impact assessment method is a recognised code
Passed
Why it matters Free text in place of a code splits one method into several spellings, so filtering by method misses some of its values.
Green-electricity zeros are not rated below market-based peers
Passed
Why it matters A green-contract zero is the contract's own figure. Marked down for being zero, it would lose to less relevant values when you look up contracted supply.
An avoided credit is linked to the burden it belongs to
Passed
Why it matters Served on its own, a credit reads as a factor in its own right. Linked beside its burden, it applies only where it belongs and is never subtracted twice.
Every value is typed as specific, generic or average
Passed
Why it matters The type says how closely a figure fits the product you bought. Any other word would be invisible to a filter on it.
The market-based value is the default
Passed
Why it matters The default then matches the figure most Scope 2 reports lead with, and a green-tariff zero is never the default when another figure exists.
Validity dates are the publisher's own, never guessed
Passed
Why it matters A start date we invented looks just like one the publisher printed, and would hide correct factor values from a search for what applied on a given date.
Quality breakdowns use their scheme's axes
Passed
Why it matters A score on an axis the scheme does not define, or off its scale, cannot be read, so the breakdown behind a rating would mislead.
No battery-electric vehicle carries tailpipe emissions
Passed
Why it matters An electric vehicle has no tailpipe. A non-zero combustion figure means its electricity emissions sit in the wrong place, or are counted twice.
The text of each estimated electricity total matches its current figures
Passed
Why it matters The description of an estimated electricity total states its year, mix, quality and the parts it adds up. If those moved, the text would explain a different number than the one served.
Every estimated factor carries its description in each language
Passed · 16 in all libraries
Why it matters An estimated factor is one we computed, not one a publisher printed. Its description says so and names the data behind it. Without it, you could not tell the estimate from a published figure.
The text of each estimated factor matches its current figures
Passed
Why it matters An estimated factor's description states the year, shares and quality behind it. If those moved, the text would explain a different number than the one served.
A total built on an estimated part is marked as estimated
Passed
Why it matters If the total lost the mark, you would read a figure we partly computed as one the publisher printed.
Every estimate is built only from data we may redistribute
Passed
Why it matters An estimate derived from restricted data would pass that data on under our open licence, which its owner never allowed.
No estimated factor is rated above the data it was built from
Passed
Why it matters An estimate cannot be more reliable than its inputs. Rating it higher would lead you to trust it more than a published figure.
No estimate sits beside a total of unclear scope
Passed
Why it matters When the publisher does not say whether its total includes a stage, our estimate of that stage may count it twice. These cases are listed for review.
No estimate repeats a stage the publisher's total already includes
Passed · 2 in all libraries
Why it matters If the publisher's figure already covers, say, grid losses, adding our estimate of those losses would count them twice and overstate your emissions.
Every factor we complete has all of its estimated parts
Passed · 7 in all libraries
Why it matters If one part, such as grid losses, is missing where the others were estimated, a total built from them silently leaves that part out.
No estimate is served where the publisher printed the figure
Passed · 25 in all libraries
Why it matters When the publisher states the number itself, theirs is the one to use. An estimate beside it would give you two answers to the same question.
We only estimate for publishers whose rule allows it
Passed
Why it matters Some publishers print every part themselves, or are deliberately left as they are. An estimate added to them would mix our numbers into theirs, against the rule set for that library.
Every estimated factor still matches the inputs it was computed from
Passed
Why it matters When an input is revised or withdrawn, the estimate built on it is out of date until it is recomputed.
No estimated total competes with a published one
Passed · 24 in all libraries
Why it matters Where the publisher prints a total for the same activity, region and year, an estimated total beside it would give you two answers to the same question.
Every factor with a current value has a default
Passed
Why it matters A factor with values but no default is left out of the served catalogue, so you would never find it in search or exports.
Every factor has a value, in a library that publishes values
Passed
Why it matters A factor listed with no number looks like a match in search but gives you nothing to calculate with.
The text of each fuel supply-chain estimate matches its current figures
Passed
Why it matters Its description states the year, the figures, the ratio and the quality behind the estimate. If those moved, the text would explain a different number than the one served.
No fuel supply-chain estimate is rated above what its method allows
Passed
Why it matters Each way of estimating a fuel's supply chain has a highest rating it can earn, and an estimate never outranks the combustion figure it builds on. A better rating would lead you to trust it more than it deserves.
Every fuel estimate is built only from data we may redistribute
Passed
Why it matters An estimate derived from restricted data would pass that data on under our open licence, which its owner never allowed.
Every fuel eligible for a supply-chain estimate is classified
Passed
Why it matters The supply-chain estimate depends on which fuel is burned. A fuel nobody has classified gets no estimate, so you would miss that part of its emissions without knowing why.
No fuel estimate is served where the publisher printed the supply-chain figure
Passed
Why it matters When the publisher states the figure itself, theirs is the one to use. An estimate beside it would give you two answers to the same question.
No supply-chain estimate is served for a fuel we deliberately left out
Passed
Why it matters Some fuels are left out on purpose, for instance when no published supply-chain figure fits them. An estimate on one of them would be a number we decided not to stand behind.
Every fuel supply-chain estimate still matches the figures it was computed from
Passed
Why it matters The estimate scales the publisher's combustion figure by a supply-chain ratio taken from other published data. When either is revised or withdrawn, the estimate is out of date until it is recomputed.
Every tagged gas has a known GWP
Passed
Why it matters A kilogram of one named gas is restated in AR6 with that gas's own GWP. A tag the GWP table does not carry would leave the value unconverted, or convert it with the wrong number.
Every fixed group of regions lists what it covers
Passed
Why it matters A group like “Europe outside the EU” with no member list cannot be placed, so its factor values never match a search for any country in it.
Where both exist, the residual mix is shown before the green-tariff zero
Passed
Why it matters Green electricity counts as zero only for buyers who hold the matching certificates. Showing zero by default would understate everyone else's emissions.
Every green-electricity zero is a market-based value
Passed
Why it matters A zero from a green contract only holds for the buyer of that contract. Filed as location-based, it would put a zero on the physical grid.
Every electricity factor states its mix
Passed
Why it matters Without its mix you cannot tell a location-based figure from a market-based one, and Scope 2 reporting needs both side by side.
The newest edition of each value is the one marked current
Passed
Why it matters If an older edition stayed marked as current, you would get superseded numbers, or two answers for the same factor.
Every publisher has a rule on whether we estimate its missing parts
Passed
Why it matters For electricity and fuels we can estimate parts a publisher leaves out, such as grid losses or the fuel supply chain. Without a rule, a missing part could be a gap or a deliberate choice, so nothing is estimated until one is set.
Factor descriptions describe the factor, not the whole library
Passed
Why it matters When the same long text is repeated on every factor, it tells you nothing about the one you are looking at and hides what is specific to it.
Every library's licence has its rights recorded
Passed
Why it matters Without them, the library page cannot tell you what you may do with the data: share it, change it or use it commercially.
No fossil electricity mix has a zero fuel supply chain
Passed
Why it matters Electricity with fossil emissions always has a supply chain behind it: extracting and transporting the fuel. A zero there means the chain was priced from the wrong mix. Green power is the exception: its chain covers only biomass, and is a real zero on a grid that burns none.
Every green-electricity zero is exactly zero and says why
Passed
Why it matters A green-tariff factor is zero by rule. Any other number, or a zero with no stated reason, would mean the rule was applied wrongly.
Green-electricity zeros cover power generation only
Passed
Why it matters Certificates cover the power plant's emissions, not grid losses or the upstream fuel chain. A zero on those stages would understate your Scope 2 and Scope 3 figures.
Only a total we computed may mix GWP vintages
Passed
Why it matters A published row states one GWP vintage. A mix of AR5 and AR6 can only come from a total assembled out of several rows, and saying so tells you the number was computed, not published.
Spend factors state their price year and basis
Passed
Why it matters A 2019 euro is not a 2024 euro, and a purchaser price includes margins a basic price does not. Without both, spend footprints drift.
One default value per factor and year
Passed
Why it matters Two defaults for one year give two answers to the same lookup.
Every value has a number, a GWP version and a reference year
Passed
Why it matters Without the number there is nothing to multiply. Without the GWP version or the year, you cannot tell whether two values are comparable.
No factor description is too long to display in full
Known limitation · 3 in this library · 28 in all libraries
Why it matters Text beyond the limit is cut short on the factor page, so part of what the publisher wrote shows only in the download.
The library-wide answers on what a factor covers are up to date
Passed
Why it matters Some questions, such as whether a figure includes transport, are answered once for a whole library. If the stored answers fall behind, a factor's details can tell you something we no longer state.
Every library-wide answer applies to at least one factor
Passed · 3 in all libraries
Why it matters An answer about a category or stage the library no longer covers changes nothing you see. It is listed so it can be removed.
Every excused arithmetic disagreement is stated
Passed
Why it matters Where a publisher's own total does not equal its parts and we serve it anyway, the exception is listed on every audit run rather than left in code where nobody sees it.
Every reference year falls between 1960 and next year
Passed
Why it matters A year outside that range points to a typo or a misread column, and would put the value in the wrong period when you filter by year.
The parts of a total are never listed twice under one label
Passed
Why it matters A group that repeats a part label is a list of terms, not a split of the total, so adding its rows up would count some emissions twice.
Every residual mix has its green-tariff counterpart
Passed
Why it matters Market-based Scope 2 reporting needs both: the residual mix for ordinary contracts and a zero for certified green power. With one missing, you have to find it elsewhere.
Every publisher's quality rating system is read
Passed
Why it matters If we do not read a publisher's rating system, its values are treated as unrated and marked down, although the publisher rated them.
Every factor is filed under the most specific category its source allows
Passed · 1,852 in all libraries
Why it matters Some factors sit in a broad category because their source covers several narrower ones. They are listed so a finer mapping can place them more precisely where the source allows it.
Every factor has a category
Passed
Why it matters A factor with no category drops out of every category filter and comparison. Without this check, a library with no category mapping would load unlabelled, and nothing would say so.
Every categorised factor has a GHG Protocol scope
Known limitation · 1 in this library · 30 in all libraries
Why it matters Without a scope, you cannot tell whether the factor belongs in Scope 1, 2 or 3 of your inventory, and you have to place it yourself.
Single-gas values have their AR6 version
Passed · 5 in all libraries
Why it matters A kilogram of one refrigerant is worth its GWP, so it can be restated in AR6 exactly. Blends and untagged gases stay on their published vintage, which can move a leak's footprint by several percent or more.
No factor answers a question that does not arise for it
Known limitation · 1 in this library · 5 in all libraries
Why it matters Some questions only make sense for some kinds of factor. An answer where the question should not arise is either misplaced, or a sign the kind is too coarse for that factor, so each case is reviewed.
A part covering the same scope as its total is linked to it
Passed
Why it matters When a part and the total beside it cover exactly the same scope, nothing in the numbers tells them apart. Linking them stops you adding a part to the total that already contains it.
A year in a factor's name matches its reference year
Passed
Why it matters A name like “Grid 2019” on a 2023 value usually means a yearly series was flattened, so you could apply one year's figure to another.

How the audit works

What can I do with this data?

Restricted licence · credit the publisher

Your rights

Restricted licence · epd-norge-digi-terms

Use it to calculate my own footprint: Yes
Publish my footprint results: Yes, if
you credit the publisher
Share the file with my customers: Ask EPD-Norge (Næringslivets Stiftelse for Miljødeklarasjoner)
Put the factors in a product I sell: Ask EPD-Norge (Næringslivets Stiftelse for Miljødeklarasjoner)
Modify it or combine it with my own data: No

Publisher's published terms, checked on 2 Oct 2026

Digi terms preamble: "Any further commercial use of the data, circulating it to third parties, requires entering into a licensing agreement." Section 3: "The content of the online data must not be changed or imitated." Section 5.1: cite the EPDs as the source. No deletion or return clause.

Credit line

EPD-Norge (EPD Global), EPD data from https://epdnorway.lca-data.com. Normalised by open-climate.ai, https://open-climate.ai/factors/libraries/epd_norge/ (CC BY 4.0)

Not legal advice: the publisher's terms prevail.

Full terms

How to read these answers

Coverage

Browse factors

top 0 matches

Saved	Unfold	Factor	Region	Boundary	Unit

Versions

How this works

Version	Published	Loaded	Status	Source
EPD_NORGE_2026-10-02	2 Oct 2026	5 Oct 2026	Served	Source

Methodology

How this works

Values are global warming potential per declared unit (per kg, m³, m², m, MJ or piece), reported per life cycle module: A1-A3 product stage, A4-A5 construction, B1-B7 use, C1-C4 end of life, and D, benefits beyond the system boundary.
Most datasets follow EN 15804+A2, with the EF 3.0 or EF 3.1 characterisation, and the served number is GWP-fossil, with the total, biogenic and land use parts kept beside it. Older datasets follow EN 15804+A1 and print a single total, which we serve and flag.
No breakdown by gas is published, so the values cannot be restated in AR6.
Each EPD gets one total over the modules it declares, built the same way as for ÖKOBAUDAT: cradle to gate for A1-A3, cradle to grave when every A to C module is declared. Where the EPD prints A1, A2 and A3 without their sum, the cradle to gate total is their sum; where it prints the sum, the parts are linked under it. Module D is shown beside the total, never added to it.
The reference year is the dataset's own reference year. The 86 datasets that state none are given 2024.
Datasets an EPD calls generic are modelled background data and name no supplier. Every other dataset is product or manufacturer specific.

Mixed: the EPD's declared ILCD reference year, which is a data year on Kiwa-EE and most often the year the EPD was published on the other nodes. An EPD that states none is dated off its own publication or entry date.

What we import

The node as harvested on 2026-10-02: about 12,900 of the 12,998 datasets it lists, covering 12,069 registered EPDs plus 477 datasets with no registration number, one factor per module.
The declaration owner is shown as the supplier.
Each dataset is placed in an open-climate.ai category, read from EPD-Norge's own product classes, the ÖKOBAUDAT classes some datasets carry, the EPD's folder on the register, its product category rules or, for a few, its name.
Values declared per tonne or another amount are converted to the declared unit.
Not imported: the 5 EPDs the register marks as withdrawn, templates and test uploads, datasets with no GWP result or with every module at zero, datasets whose declared unit cannot be resolved, and the EN 15804 indicators other than GWP.
About three in four names are published in English. The others, in Norwegian, Danish, Swedish or German, are shown in our English translation, marked as translated.

Licence

How this works

Restricted. The EPD-Global Digi terms allow free use for your own life cycle assessments and require the EPDs to be cited as the source (section 5.1); "any further commercial use of the data, circulating it to third parties, requires entering into a licensing agreement", and the content "must not be changed or imitated" (section 3). Holding the values for your own footprint and publishing results that cite the EPD are allowed; sharing and embedding them need EPD-Norge's agreement, which we are requesting, and modifying them is not allowed. Until then the values are not shown on the public site. Attribution: "EPD-Norge (EPD Global), EPD data from https://epdnorway.lca-data.com". Last verified 2026-10-02.

What can I do with this data?

Credit line: EPD-Norge (EPD Global), EPD data from https://epdnorway.lca-data.com

epd-norge-digi-terms

Any further commercial use of the data, circulating it to third parties, requires entering into a licensing agreement.

Limitations

About 1,200 datasets are past their validity date. The register still lists them, so they are loaded; check an EPD's validity date before use.
Datasets that state no location are placed in the world as a whole, and marked as an assigned location, not a published one.
Some product names carry a year one to three years before the dataset's reference year, for example "CEM I 42,5 R Hannover, 2025" with reference year 2026. They are loaded as published.
18 values declare a fossil uptake no kilogram of product can hold: 16 of them one Danish wall series (module B1 at -2,350 kg CO2e per tonne beside 80.7 for A1), plus a hollow-core slab and an aluminium end-of-life module. They are flagged as problematic and not served.
Some language tags on the register are wrong (dk, or a web address), so a name may be tagged with a language it is not written in.

Changelog

2026-10-02: node harvest of 2026-10-02 loaded.
2026-10-05: the characterisation model is read from the climate indicator itself; implausible fossil uptakes are flagged; names not published in English are shown in an English translation.

Know a newer edition?

If EPD-Norge has published an edition we do not serve yet, tell us where to find it.