BIZTRAC BETA
Rental and operating of own or leased real estate

SANDSLIHAUGEN 30 AS

Org. no. 979455771 Limited company (AS) Oslo Incorporated 1997 Active
Ownership graph ↗
Revenue 2024 NOK 1.4m
Operating profit NOK −4.3m
Equity NOK 3.0m
Incorporated 1997
Share capital NOK 2.3m

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−4,3 mill kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SANDSLIHAUGEN 30 AS is registered as a limited company in Oslo, Oslo with organisation number 979455771. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1997. Registered share capital is NOK 2.3m, divided into 1 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom eller andeler heri, samt alt hva derved står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.4m in revenue and NOK −4.3m in operating profit.

Key figures · 2024

Revenue
NOK 1.4m
Operating profit
NOK −4.3m
Equity
NOK 3.0m
Est. value
NOK 2.7m

Financial health · 2024

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

Who owns SANDSLIHAUGEN 30 AS?

URBAN PROPERTY EIER AS
SANDSLIHAUGEN 30 AS
NOK 1.4m rev. · NOK −4.3m profit

SANDSLIHAUGEN 30 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDSLIHAUGEN 30 AS

Who owns SANDSLIHAUGEN 30 AS?

URBAN PROPERTY EIER AS is the largest registered owner, with 100.0%.

What is the revenue of SANDSLIHAUGEN 30 AS?

SANDSLIHAUGEN 30 AS had revenue of NOK 1.4m in 2024.

Where is SANDSLIHAUGEN 30 AS based?

SANDSLIHAUGEN 30 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.