BIZTRAC BETA
Uoppgitt

SALVESEN INVEST AS

Org. no. 928677605 Limited company (AS) Bærum Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −32,000
Equity NOK 446,000
Incorporated 2022
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−32k kr).

SALVESEN INVEST AS is registered as a limited company in Bærum, Akershus with organisation number 928677605. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −32,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −32,000
Equity
NOK 446,000
Est. value
NOK 2.5m

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
11.4%
Satisfactory
Equity as a share of total capital

Who owns SALVESEN INVEST AS?

SIMEN MATHIAS SALVESEN ØRNES
SALVESEN INVEST AS
NOK 0 rev. · NOK −32,000 profit

SALVESEN INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SALVESEN INVEST AS own?

SALVESEN INVEST AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SALVESEN INVEST AS

Who owns SALVESEN INVEST AS?

SIMEN MATHIAS SALVESEN ØRNES is the largest registered owner, with 100.0%.

What is the revenue of SALVESEN INVEST AS?

SALVESEN INVEST AS had revenue of NOK 0 in 2025.

Who is the general manager of SALVESEN INVEST AS?

Simen Mathias Salvesen Ørnes is registered as general manager of SALVESEN INVEST AS.

Where is SALVESEN INVEST AS based?

SALVESEN INVEST AS has its business address in Fornebu.

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.