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

BM3 INVEST AS

Org. no. 916725477 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Operating profit NOK −14,000
Equity NOK −40.2m
Incorporated 2016
Share capital NOK 8.0m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−40,2 mill kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−14k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

BM3 INVEST AS is registered as a limited company in Oslo, Oslo with organisation number 916725477. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2016. Registered share capital is NOK 8.0m, divided into 80000 shares. The company's stated purpose is: “Investeringsselskap og skal eie aksjer i andre selskaper.”.

Former names: STARTUP 41 16 AS

Key figures · 2025

Operating profit
NOK −14,000
▲ +80 %
Equity
NOK −40.2m
▼ −1 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
-892.7%
Not satisfactory
Return on total assets
Solidity
-20504868.9%
Weak
Equity as a share of total capital

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

Who owns BM3 INVEST AS?

BM3 INVEST AS
· NOK −14,000 profit

BM3 INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BM3 INVEST AS own?

BM3 INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BM3 INVEST AS

Who owns BM3 INVEST AS?

KARA INVEST AS is the largest registered owner, with 100.0%.

Where is BM3 INVEST AS based?

BM3 INVEST 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.