Consumption per DK10 Industry Code, Region and Year

Open data API in a single place

Provided by Energinet

Get early access to Consumption per DK10 Industry Code, Region and Year API!

Let us know and we will figure it out for you.

Dataset information

Catalog

Energinet catalog

Country of origin

Denmark

Updated

2026.03.03 06:18

Created

2025.09.21

Available languages

English

Keywords

elforsyningsstatistik, energistatistik, elforsyning, Energi, el, forbrug af el, forbrug af elektricitet, elforbrug, energi, elektricitet, energidata

Datasource

Official portal for European data link

Quality scoring

Dataset description

Yearly consumption of industries divided by municipality code and DK10 industry code, which is based on Statistics Denmark. The dataset is updated yearly in the first quarter of the year. To comply with laws regarding the protection of private data, **methods for anonymizing data have been applied**. This dataset uses number and dominance as a criterion for confidentiality. The number criteria is set to 20 and the dominance criteria is set so that 2 units combined maximum may contain 90 percent per year. In case of the criteria being exceeded, the dataset will combine data columns or aggregate data columns to a high level in the following order: 1. Regions being combined and/or aggregated 2. DK10 codes being combined 3. Years being combined

European data infrastructure with broad catalog discovery, free evaluation access and production-grade API options.

190K+

indexed dataset pages

countries and EU institutions

2019

API-first since

Free API quota

for evaluation and prototypes

SLA

history and push on production APIs

FAQ

Questions before production use

Practical answers on evaluation, licensing, freshness, versioning and support.

api.store is built and operated by Apitalks s.r.o. Company details and a direct contact path are linked in the footer for vendor checks and procurement review.

Yes. Selected APIs include a free API quota, so your team can validate coverage, freshness, response shape and workflow fit before asking for a production plan.

Often yes, but usage rights depend on the source license and dataset. We surface source, license and update metadata where available, and can help review terms before a production integration.

Maintained APIs include update metadata where available. For production integrations, we can add history, monitoring and push updates so changes are easier to detect and act on.

Production APIs can add SLA, stable identifiers, versioning support, history, push updates and direct support around the data your product or AI workflow depends on.

Didn't find the API you need?

Let us know and we will figure it out for you.

api.store Built by Apitalks

European data discovery with free evaluation access and production-grade API options.

About api.storePrivacy Terms of Service