biztrac. BETA
COMPANY REGISTER PROFILE
923150765 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Development of building projects

SPOR EIENDOMSPARTNER AS

Org. no. 923150765 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Operating profit NOK −129,000
Equity NOK −471,000
Incorporated 2019
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−471k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−129k kr).

SPOR EIENDOMSPARTNER AS is registered as a limited company in Oslo, Oslo with organisation number 923150765. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2019. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering, utvikling, salg og utleie av fast eiendom, og dertil annen virksomhet med samme eller lignende formål.”.

Key figures · 2025

Operating profit
NOK −129,000
▼ −173 %
Equity
NOK −471,000
▼ −177 %
Est. value
NOK 211,000

Financial health · 2025

Liquidity
16.27
Very good
Current assets ÷ current liabilities
Profitability
-0.2%
Not satisfactory
Return on total assets
Solidity
-0.5%
Weak
Equity as a share of total capital

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

Who owns SPOR EIENDOMSPARTNER AS?

SPOR EIENDOMSPARTNER AS
· NOK −129,000 profit

SPOR EIENDOMSPARTNER AS has 2 registered shareholders:

All shareholders and roles →

Which companies does SPOR EIENDOMSPARTNER AS own?

SPOR EIENDOMSPARTNER AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about SPOR EIENDOMSPARTNER AS

Who owns SPOR EIENDOMSPARTNER AS?

JMB INVEST AS is the largest registered owner, with 50.0%.

Where is SPOR EIENDOMSPARTNER AS based?

SPOR EIENDOMSPARTNER 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.