BIZTRAC BETA
Rental and operating of own or leased real estate

BL EIGEDOM AS

Org. no. 924854286 Limited company (AS) Bjørnafjorden Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 907,000
Operating profit NOK 550,000
Equity NOK −2.4m
Incorporated 2020
Share capital NOK 400,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−2,4 mill kr).

BL EIGEDOM AS is registered as a limited company in Bjørnafjorden, Vestland with organisation number 924854286. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2020. Registered share capital is NOK 400,000, divided into 400000 shares. The company's stated purpose is: “Eie og forvalte aksjer, samt investere og leie ut fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 907,000 in revenue and NOK 550,000 in operating profit.

Key figures · 2025

Revenue
NOK 907,000
Operating profit
NOK 550,000
Equity
NOK −2.4m
Est. value
NOK 3.3m

Financial health · 2025

Liquidity
0.34
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-41.4%
Weak
Equity as a share of total capital

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

Who owns BL EIGEDOM AS?

ØYVIND LYSSAND HOLDING AS
BL EIGEDOM AS
NOK 907,000 rev. · NOK 550,000 profit

BL EIGEDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BL EIGEDOM AS

Who owns BL EIGEDOM AS?

ØYVIND LYSSAND HOLDING AS is the largest registered owner, with 50.0%.

What is the revenue of BL EIGEDOM AS?

BL EIGEDOM AS had revenue of NOK 907,000 in 2025.

Who is the general manager of BL EIGEDOM AS?

Bjarte Bøe is registered as general manager of BL EIGEDOM AS.

Where is BL EIGEDOM AS based?

BL EIGEDOM AS has its business address in Os.

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.