BIZTRAC BETA
Business and other management consultancy activities

CORTAVIK AS

Org. no. 926043552 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 139,000
Operating profit NOK −29,000
Equity NOK 535,000
Incorporated 2020
Share capital NOK 250,000

Signals

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

CORTAVIK AS is registered as a limited company in Bærum, Akershus with organisation number 926043552. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2020. Registered share capital is NOK 250,000, divided into 500000 shares. The company's stated purpose is: “Levere konsulenttjenester innen finans, strategi og ledelse samt tilhørende aktiviteter. I tillegg Investering i aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 139,000 in revenue and NOK −29,000 in operating profit.

Key figures · 2025

Revenue
NOK 139,000
Operating profit
NOK −29,000
Equity
NOK 535,000
Est. value
NOK 407,000

Financial health · 2025

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

Who owns CORTAVIK AS?

STEPHANE-EDOUARD ARNAUD CORTADELLAS
CORTAVIK AS
NOK 139,000 rev. · NOK −29,000 profit

CORTAVIK AS has 2 registered shareholders:

All shareholders and roles →

Which companies does CORTAVIK AS own?

CORTAVIK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about CORTAVIK AS

Who owns CORTAVIK AS?

STEPHANE-EDOUARD ARNAUD CORTADELLAS is the largest registered owner, with 90.0%.

What is the revenue of CORTAVIK AS?

CORTAVIK AS had revenue of NOK 139,000 in 2025.

Where is CORTAVIK AS based?

CORTAVIK AS has its business address in Haslum.

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.