BIZTRAC BETA
Rental and operating of own or leased real estate

SM BOLIG OG EIENDOMSINVEST AS

Org. no. 921485840 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −139,000
Equity NOK 75.0m
Incorporated 2018
Share capital NOK 4.5m

Signals

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

SM BOLIG OG EIENDOMSINVEST AS is registered as a limited company in Oslo, Oslo with organisation number 921485840. 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 4.5m, divided into 50000 shares. The company's stated purpose is: “Investeringsvirksomhet herunder kjøp og salg av aksjer, investering i fast eiendom samt andre selskaper.”.

Key figures · 2024

Operating profit
NOK −139,000
Equity
NOK 75.0m
Est. value
NOK 121.8m

Financial health · 2024

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
74.1%
Very good
Equity as a share of total capital

Who owns SM BOLIG OG EIENDOMSINVEST AS?

HORTULAN EIENDOM AS
SM BOLIG OG EIENDOMSINVEST AS
· NOK −139,000 profit

SM BOLIG OG EIENDOMSINVEST AS has 3 registered shareholders:

All shareholders and roles →

Which companies does SM BOLIG OG EIENDOMSINVEST AS own?

SM BOLIG OG EIENDOMSINVEST AS holds stakes in 8 companies:

See the full ownership structure →

Frequently asked questions about SM BOLIG OG EIENDOMSINVEST AS

Who owns SM BOLIG OG EIENDOMSINVEST AS?

HORTULAN EIENDOM AS is the largest registered owner, with 47.5%.

Where is SM BOLIG OG EIENDOMSINVEST AS based?

SM BOLIG OG EIENDOMSINVEST 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.