biztrac. BETA
COMPANY REGISTER PROFILE
919495057 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

B EIENDOM HOLDING AS

Org. no. 919495057 Limited company (AS) Hadsel Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 2.6m
Incorporated 2017
Share capital NOK 153,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−18k kr).

B EIENDOM HOLDING AS is registered as a limited company in Hadsel, Nordland with organisation number 919495057. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 153,000, divided into 102 shares. The company's stated purpose is: “Eie aksjer i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
▲ +54 %
Equity
NOK 2.6m
▼ −1 %
Est. value
NOK 2.4m

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.3%
Not satisfactory
Return on total assets
Solidity
50.2%
Very good
Equity as a share of total capital

Who owns B EIENDOM HOLDING AS?

B EIENDOM HOLDING AS has 4 registered shareholders:

All shareholders and roles →

Which companies does B EIENDOM HOLDING AS own?

B EIENDOM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about B EIENDOM HOLDING AS

Who owns B EIENDOM HOLDING AS?

Trond Bottolfsen is the largest registered owner, with 35.3%.

What is the revenue of B EIENDOM HOLDING AS?

B EIENDOM HOLDING AS had revenue of NOK 0 in 2025.

Where is B EIENDOM HOLDING AS based?

B EIENDOM HOLDING AS has its business address in Stokmarknes.

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

Report a problem

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