BIZTRAC BETA
Rental and operating of own or leased real estate

SOESTO EIENDOM AS

Org. no. 921110677 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 448,000
Operating profit NOK 338,000
Equity NOK −523,000
Incorporated 2018
Share capital NOK 60,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−523k kr).

SOESTO EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 921110677. 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 60,000, divided into 3000 shares. The company's stated purpose is: “Utleie og utvikling av fast eiendom, samt om ønskelig også å eie eller delta i selskaper med beslektet virksomhet, samt å forvalte selskapets verdier gjennom investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 448,000 in revenue and NOK 338,000 in operating profit.

Key figures · 2025

Revenue
NOK 448,000
Operating profit
NOK 338,000
Equity
NOK −523,000
Est. value
NOK 2.3m

Financial health · 2025

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

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

Who owns SOESTO EIENDOM AS?

ANDREAS STØRMER-NILSEN
SOESTO EIENDOM AS
NOK 448,000 rev. · NOK 338,000 profit

SOESTO EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SOESTO EIENDOM AS

Who owns SOESTO EIENDOM AS?

ANDREAS STØRMER-NILSEN is the largest registered owner, with 50.0%.

What is the revenue of SOESTO EIENDOM AS?

SOESTO EIENDOM AS had revenue of NOK 448,000 in 2025.

Where is SOESTO EIENDOM AS based?

SOESTO 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.