BIZTRAC BETA
Development of building projects

LDEK EIENDOM AS

Org. no. 925748005 Limited company (AS) Oslo Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −92,000
Equity NOK −325,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−325k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−92k kr).

LDEK EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 925748005. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, utvikling, og salg av eiendom samt det som naturlig står i forbindelse med dette, prosjektledelse og teknisk rådgivning. Samt byggetjenester i forbindelse med oppføring og rehabilitering av bygg.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −92,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −92,000
Equity
NOK −325,000

Financial health · 2025

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

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

Who owns LDEK EIENDOM AS?

LDEK HOLDING AS
LDEK EIENDOM AS
NOK 0 rev. · NOK −92,000 profit

LDEK EIENDOM AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about LDEK EIENDOM AS

Who owns LDEK EIENDOM AS?

LDEK HOLDING AS is the largest registered owner, with 33.3%.

What is the revenue of LDEK EIENDOM AS?

LDEK EIENDOM AS had revenue of NOK 0 in 2025.

Where is LDEK EIENDOM AS based?

LDEK EIENDOM AS has its business address in Oslo.

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.