BIZTRAC BETA
Rental and operating of own or leased real estate

SØRUMDAL EIENDOM AS

Org. no. 820215192 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −16,000
Equity NOK −1.4m
Incorporated 2017
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−1,4 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−16k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SØRUMDAL EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 820215192. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investering i, utleie og utvikling av fast eiendom, herunder deltakelse i andre selskaper med lignende virksomhet.”.

Key figures · 2025

Operating profit
NOK −16,000
Equity
NOK −1.4m

Financial health · 2025

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

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

Who owns SØRUMDAL EIENDOM AS?

CLIFF EIENDOM AS
SØRUMDAL EIENDOM AS
· NOK −16,000 profit

SØRUMDAL EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SØRUMDAL EIENDOM AS own?

SØRUMDAL EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about SØRUMDAL EIENDOM AS

Who owns SØRUMDAL EIENDOM AS?

CLIFF EIENDOM AS is the largest registered owner, with 65.0%.

Where is SØRUMDAL EIENDOM AS based?

SØRUMDAL 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.