BIZTRAC BETA
Rental and operating of own or leased real estate

KL EIGENDOM AS

Org. no. 932955687 Limited company (AS) Sogndal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −71,000
Equity NOK 150,000
Incorporated 2024
Share capital NOK 150,000

Signals

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

KL EIGENDOM AS is registered as a limited company in Sogndal, Vestland with organisation number 932955687. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2024. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Kjøp, salg, utvikling og utleie av eiendom og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −71,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −71,000
Equity
NOK 150,000
Est. value
NOK 137,000

Financial health · 2024

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

Who owns KL EIGENDOM AS?

KOLLSETE OG LIHEIM BYGGTEAM AS
KL EIGENDOM AS
NOK 0 rev. · NOK −71,000 profit

KL EIGENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about KL EIGENDOM AS

Who owns KL EIGENDOM AS?

KOLLSETE OG LIHEIM BYGGTEAM AS is the largest registered owner, with 100.0%.

What is the revenue of KL EIGENDOM AS?

KL EIGENDOM AS had revenue of NOK 0 in 2025.

Where is KL EIGENDOM AS based?

KL EIGENDOM AS has its business address in Slinda.

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.