BIZTRAC BETA
Development of building projects

LØLAND EIENDOM AS

Org. no. 922915407 Limited company (AS) Lyngdal Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −23,000
Equity NOK −96,000
Incorporated 2019
Share capital NOK 200,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−96k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−23k kr).

LØLAND EIENDOM AS is registered as a limited company in Lyngdal, Agder with organisation number 922915407. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kjøp av tomter og oppføring av hus og hytter for salg.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −23,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −23,000
Equity
NOK −96,000

Financial health · 2024

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

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

Who owns LØLAND EIENDOM AS?

H K S BYGG AS
LØLAND EIENDOM AS
NOK 0 rev. · NOK −23,000 profit

LØLAND EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LØLAND EIENDOM AS

Who owns LØLAND EIENDOM AS?

H K S BYGG AS is the largest registered owner, with 50.5%.

What is the revenue of LØLAND EIENDOM AS?

LØLAND EIENDOM AS had revenue of NOK 0 in 2024.

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

Espen Løland is registered as general manager of LØLAND EIENDOM AS.

Where is LØLAND EIENDOM AS based?

LØLAND EIENDOM AS has its business address in Konsmo.

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.