BIZTRAC BETA
Rental and operating of own or leased real estate

K LIE EIENDOM AS

Org. no. 921012551 Limited company (AS) Aure Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 3.5m
Operating profit NOK −485,000
Equity NOK −484,000
Incorporated 2018
Share capital NOK 480,000

Signals

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

K LIE EIENDOM AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 921012551. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2018. Registered share capital is NOK 480,000, divided into 1600 shares. The company's stated purpose is: “Utleie”. The most recent filed accounts, for the 2024 financial year, show NOK 3.5m in revenue and NOK −485,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.5m
Operating profit
NOK −485,000
Equity
NOK −484,000

Financial health · 2024

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

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

Who owns K LIE EIENDOM AS?

Kristine Lie
K LIE EIENDOM AS
NOK 3.5m rev. · NOK −485,000 profit

K LIE EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about K LIE EIENDOM AS

Who owns K LIE EIENDOM AS?

Kristine Lie is the largest registered owner, with 50.0%.

What is the revenue of K LIE EIENDOM AS?

K LIE EIENDOM AS had revenue of NOK 3.5m in 2024.

Who is the general manager of K LIE EIENDOM AS?

Kristine Lie is registered as general manager of K LIE EIENDOM AS.

Where is K LIE EIENDOM AS based?

K LIE EIENDOM AS has its business address in Tustna.

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.