BIZTRAC BETA
Other captive investment companies

HOØEN HOLDING AS

Org. no. 916260903 Limited company (AS) Ørland Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −63,000
Equity NOK 14.7m
Incorporated 2015
Share capital NOK 100,000

Signals

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

HOØEN HOLDING AS is registered as a limited company in Ørland, Trøndelag with organisation number 916260903. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 100,000, divided into 1 shares. The company's stated purpose is: “Forvaltning av selskapets verdier og investeringer av enhver art og annen beslektet virksomhet, herunder utlån av selskapets verdier, samt å delta i andre selskaper av enhver art.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −63,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −63,000
Equity
NOK 14.7m
Est. value
NOK 16.5m

Financial health · 2024

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

Who owns HOØEN HOLDING AS?

SIW ANITA HOØEN
HOØEN HOLDING AS
NOK 0 rev. · NOK −63,000 profit

HOØEN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOØEN HOLDING AS own?

HOØEN HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HOØEN HOLDING AS

Who owns HOØEN HOLDING AS?

SIW ANITA HOØEN is the largest registered owner, with 100.0%.

What is the revenue of HOØEN HOLDING AS?

HOØEN HOLDING AS had revenue of NOK 0 in 2024.

Where is HOØEN HOLDING AS based?

HOØEN HOLDING AS has its business address in Brekstad.

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.