biztrac. BETA
COMPANY REGISTER PROFILE
920289185 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

SHARE SPACES AS

Org. no. 920289185 Limited company (AS) Oslo Incorporated 2018 Active
Revenue 2025 NOK 33.4m
Operating profit NOK −1.8m
Equity NOK −7.8m
Incorporated 2018
Share capital NOK 3.2m

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−7,8 mill kr).

SHARE SPACES AS is registered as a limited company in Oslo, Oslo with organisation number 920289185. 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 3.2m, divided into 32142 shares. The company's stated purpose is: “Eie eller leie eiendom for så å leie ut til kontorer/kontorplasser.”. The most recent filed accounts, for the 2025 financial year, show NOK 33.4m in revenue and NOK −1.8m in operating profit.

Key figures · 2025

Revenue
NOK 33.4m
▼ −6 %
Operating profit
NOK −1.8m
▲ +66 %
Equity
NOK −7.8m
▼ −994 %

Financial health · 2025

Liquidity
0.21
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-102.8%
Weak
Equity as a share of total capital

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

Who owns SHARE SPACES AS?

SHARE SPACES AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about SHARE SPACES AS

Who owns SHARE SPACES AS?

SCANDINAVIAN FITNESS GROUP AS is the largest registered owner, with 20.0%.

What is the revenue of SHARE SPACES AS?

SHARE SPACES AS had revenue of NOK 33.4m in 2025.

Who is the general manager of SHARE SPACES AS?

Johan Andreas Melander is registered as general manager of SHARE SPACES AS.

Where is SHARE SPACES AS based?

SHARE SPACES 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.