biztrac. BETA
COMPANY REGISTER PROFILE
921117221 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Buying and selling of own real estate

SPG OMSORGSBYGG 2 AS

Org. no. 921117221 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −278,000
Equity NOK 93.9m
Incorporated 2018
Share capital NOK 902,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−278k kr).
  • Nylig endring 2026-07-15 Aksjekapital registrert 2026-07-15.

SPG OMSORGSBYGG 2 AS is registered as a limited company in Oslo, Oslo with organisation number 921117221. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2018. Registered share capital is NOK 902,000, divided into 451115 shares. The company's stated purpose is: “Investering i fast eiendom eller eierandeler i selskaper som direkte eller indirekte eier fast eiendom, verdipapirer samt annen virksomhet i tilknytning til dette.”.

Former names: SPG EIENDOM 24 AS

Key figures · 2025

Operating profit
NOK −278,000
▲ +88 %
Equity
NOK 93.9m
▲ +43 %
Est. value
NOK 85.7m

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
1.1%
Weak
Return on total assets
Solidity
19.3%
Good
Equity as a share of total capital

Who owns SPG OMSORGSBYGG 2 AS?

SPG OMSORGSBYGG 2 AS has 9 registered shareholders:

All shareholders and roles →

Which companies does SPG OMSORGSBYGG 2 AS own?

SPG OMSORGSBYGG 2 AS holds stakes in 5 companies:

See the full ownership structure →

Group structure

SPG OMSORGSBYGG 2 AS er morselskap for 4 datterselskaper:

Frequently asked questions about SPG OMSORGSBYGG 2 AS

Who owns SPG OMSORGSBYGG 2 AS?

BRJ BOLIGINVEST AS is the largest registered owner, with 24.4%.

Where is SPG OMSORGSBYGG 2 AS based?

SPG OMSORGSBYGG 2 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.