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

SPG TANGEN AS

Org. no. 921116985 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Operating profit NOK −559,000
Equity NOK 37.8m
Incorporated 2018
Share capital NOK 109,000

Signals

3 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−559k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.
  • Nylig endring 2026-09-01 Aksjekapital registrert 2026-09-01.

SPG TANGEN AS is registered as a limited company in Oslo, Oslo with organisation number 921116985. 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 109,000, divided into 1094035 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 23 AS

Key figures · 2025

Operating profit
NOK −559,000
▲ +44 %
Equity
NOK 37.8m
▲ +35 %
Est. value
NOK 34.5m

Financial health · 2025

Liquidity
5.10
Very good
Current assets ÷ current liabilities
Profitability
-0.1%
Not satisfactory
Return on total assets
Solidity
11.6%
Satisfactory
Equity as a share of total capital

Who owns SPG TANGEN AS?

SPG TANGEN AS has 8 registered shareholders:

All shareholders and roles →

Which companies does SPG TANGEN AS own?

SPG TANGEN AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SPG TANGEN AS

Who owns SPG TANGEN AS?

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

Where is SPG TANGEN AS based?

SPG TANGEN 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.