BIZTRAC BETA
COMPANY REGISTER PROFILE
913659058 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Rental and operating of own or leased real estate

HEDA HOLDING AS

Org. no. 913659058 Limited company (AS) Asker Incorporated 2014 Active
Ownership graph ↗
Equity NOK 1.9m
Incorporated 2014
Share capital NOK 300,000

HEDA HOLDING AS is registered as a limited company in Asker, Akershus with organisation number 913659058. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2014. Registered share capital is NOK 300,000, divided into 10000 shares. The company's stated purpose is: “Deltakelse i andre selskaper gjennom eie aksjer og verdipapirer samt kunne forvalte avkastning av dette i annen næringsvirksomhet, utleie av egen eller leid fast eiendom, konsulentvirksomhet og utleie av arbeidskraft.”.

Key figures · 2025

Equity
NOK 1.9m
▲ +5 %
Est. value
NOK 1.6m

Financial health · 2025

Liquidity
591.53
Very good
Current assets ÷ current liabilities
Profitability
26.6%
Very good
Return on total assets
Solidity
99.8%
Very good
Equity as a share of total capital

Who owns HEDA HOLDING AS?

HEDA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HEDA HOLDING AS

Who owns HEDA HOLDING AS?

HENNING ARNE DALSEGG is the largest registered owner, with 100.0%.

Where is HEDA HOLDING AS based?

HEDA HOLDING AS has its business address in Billingstad.

Property

Business address c/o Henning Dalsegg Åsløkkveien 65B, 1396 Billingstad
Cadastral unit 3203-38/456/0/0
Building Kjede/atriumhus · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.