BIZTRAC BETA
Rental and operating of own or leased real estate

ASSET 40 AS

Org. no. 930009938 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Operating profit NOK −2.7m
Equity NOK −30.4m
Incorporated 2022
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−30,4 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−2,7 mill kr).
  • Nylig endring 2026-06-24 Adresseendring registrert 2026-06-24.

ASSET 40 AS is registered as a limited company in Oslo, Oslo with organisation number 930009938. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie fast eiendom, utleie av fast eiendom, eie aksjer i andre selskap, investere i aksjer og andre verdipapirer, samt annen virksomhet som står i naturlig tilknytning til dette.”.

Key figures · 2024

Operating profit
NOK −2.7m
Equity
NOK −30.4m

Financial health · 2024

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

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

Who owns ASSET 40 AS?

BRYNE SENTRUM UTVIKLING AS
ASSET 40 AS
· NOK −2.7m profit

ASSET 40 AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ASSET 40 AS own?

ASSET 40 AS holds a stake in 1 company:

See the full ownership structure →

Group structure

ASSET 40 AS er morselskap for 3 datterselskaper:

Frequently asked questions about ASSET 40 AS

Who owns ASSET 40 AS?

BRYNE SENTRUM UTVIKLING AS is the largest registered owner, with 100.0%.

Where is ASSET 40 AS based?

ASSET 40 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.