BIZTRAC BETA
Rental and operating of own or leased real estate

LØD EIENDOM AS

Org. no. 997534883 Limited company (AS) Bærum Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 189,000
Operating profit NOK −1.5m
Equity NOK 3.5m
Incorporated 2011
Share capital NOK 10.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−1,5 mill kr).

LØD EIENDOM AS is registered as a limited company in Bærum, Akershus with organisation number 997534883. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2011. Registered share capital is NOK 10.0m, divided into 1000 shares. The company's stated purpose is: “Drive utvikling og utleie av fast eiendom, handel, produksjon og annen økonomisk virksomhet, herunder deltakelse i norske og utenlandske selskaper.”. The most recent filed accounts, for the 2024 financial year, show NOK 189,000 in revenue and NOK −1.5m in operating profit.

Key figures · 2024

Revenue
NOK 189,000
Operating profit
NOK −1.5m
Equity
NOK 3.5m
Est. value
NOK 2.6m

Financial health · 2024

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

Who owns LØD EIENDOM AS?

HØVIK VERK AS
LØD EIENDOM AS
NOK 189,000 rev. · NOK −1.5m profit

LØD EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØD EIENDOM AS

Who owns LØD EIENDOM AS?

HØVIK VERK AS is the largest registered owner, with 50.0%.

What is the revenue of LØD EIENDOM AS?

LØD EIENDOM AS had revenue of NOK 189,000 in 2024.

Who is the general manager of LØD EIENDOM AS?

Per Gunnar Ottosson is registered as general manager of LØD EIENDOM AS.

Where is LØD EIENDOM AS based?

LØD EIENDOM AS has its business address in Høvik.

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.