BIZTRAC BETA
Rental and operating of own or leased real estate

B-L EIENDOM AS

Org. no. 931824112 Limited company (AS) Lyngdal Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK 49,000
Equity NOK −979,000
Incorporated 2023
Share capital NOK 500,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−979k kr).

B-L EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 931824112. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Utvikling, forvaltning og utleie av fast eiendom og alt som står i naturlig forbindelse med dette, herunder direkte og indirekte investeringer i foretak som driver slik virksomhet samt øvrige aksjeinvesteringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK 49,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK 49,000
Equity
NOK −979,000
Est. value
NOK 333,000

Financial health · 2025

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

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

Who owns B-L EIENDOM AS?

HENRIK STORDAL
B-L EIENDOM AS
NOK 1.0m rev. · NOK 49,000 profit

B-L EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about B-L EIENDOM AS

Who owns B-L EIENDOM AS?

HENRIK STORDAL is the largest registered owner, with 50.0%.

What is the revenue of B-L EIENDOM AS?

B-L EIENDOM AS had revenue of NOK 1.0m in 2025.

Where is B-L EIENDOM AS based?

B-L EIENDOM AS has its business address in Byremo.

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.