BIZTRAC BETA
Other activities of other membership organisations

COBE INVEST I AS

Org. no. 920640869 Limited company (AS) Tromsø Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −28,000
Equity NOK 21.9m
Incorporated 2018
Share capital NOK 6.6m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−28k kr).

COBE INVEST I AS is registered as a limited company in Tromsø, Troms with organisation number 920640869. The business is classified under other activities of other membership organisations (NACE 94.992). The company was incorporated in 2018. Registered share capital is NOK 6.6m, divided into 6628918 shares. The company's stated purpose is: “Eie og investere i aksjer og andre verdipapir, samt deltakelse av enhver art i andre virksomheter og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −28,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −28,000
Equity
NOK 21.9m
Est. value
NOK 29.1m

Financial health · 2024

Liquidity
36.30
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
76.9%
Very good
Equity as a share of total capital

Who owns COBE INVEST I AS?

CONSTO HOLDING AS
COBE INVEST I AS
NOK 0 rev. · NOK −28,000 profit

COBE INVEST I AS has 20+ registered shareholders:

All shareholders and roles →

Which companies does COBE INVEST I AS own?

COBE INVEST I AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about COBE INVEST I AS

Who owns COBE INVEST I AS?

CONSTO HOLDING AS is the largest registered owner, with 22.6%.

What is the revenue of COBE INVEST I AS?

COBE INVEST I AS had revenue of NOK 0 in 2024.

Where is COBE INVEST I AS based?

COBE INVEST I AS has its business address in Tromsø.

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.