BIZTRAC BETA
Rental and operating of own or leased real estate

BRUNHUSET HOLDING AS

Org. no. 916354657 Limited company (AS) Nærøysund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −50,000
Equity NOK 9.5m
Incorporated 2015
Share capital NOK 50,000

Signals

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

BRUNHUSET HOLDING AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 916354657. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2015. Registered share capital is NOK 50,000, divided into 500 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt investeringer og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −50,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −50,000
Equity
NOK 9.5m
Est. value
NOK 10.2m

Financial health · 2024

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

Who owns BRUNHUSET HOLDING AS?

SIV BEATE ØREN
BRUNHUSET HOLDING AS
NOK 0 rev. · NOK −50,000 profit

BRUNHUSET HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does BRUNHUSET HOLDING AS own?

BRUNHUSET HOLDING AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about BRUNHUSET HOLDING AS

Who owns BRUNHUSET HOLDING AS?

SIV BEATE ØREN is the largest registered owner, with 50.0%.

What is the revenue of BRUNHUSET HOLDING AS?

BRUNHUSET HOLDING AS had revenue of NOK 0 in 2024.

Where is BRUNHUSET HOLDING AS based?

BRUNHUSET HOLDING AS has its business address in Kolvereid.

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.