BIZTRAC BETA
Uoppgitt

HD HOLDINGS AS

Org. no. 916823274 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −5,000
Equity NOK 11,000
Incorporated 2016
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−5k kr).

HD HOLDINGS AS is registered as a limited company in Oslo, Oslo with organisation number 916823274. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investeringer i aksjer og andre verdipapirer, kjøp, utvikling og salg av fast eiendom, herunder deltakelse i andre selskaper og virksomheter, samt utførelse av ulike konsulent- og rådgivningsoppdrag.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 11,000
Est. value
NOK 13,000

Financial health · 2024

Liquidity
8.22
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
87.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns HD HOLDINGS AS?

EIRIK HUSBY DYRSET
HD HOLDINGS AS
NOK 0 rev. · NOK −5,000 profit

HD HOLDINGS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HD HOLDINGS AS

Who owns HD HOLDINGS AS?

EIRIK HUSBY DYRSET is the largest registered owner, with 100.0%.

What is the revenue of HD HOLDINGS AS?

HD HOLDINGS AS had revenue of NOK 0 in 2024.

Who is the general manager of HD HOLDINGS AS?

Eirik Husby Dyrset is registered as general manager of HD HOLDINGS AS.

Where is HD HOLDINGS AS based?

HD HOLDINGS AS has its business address in Oslo.

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

Report a problem

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