BIZTRAC BETA
Business and other management consultancy activities

KOPERVIK KAPITALFORVALTNING AS

Org. no. 990117705 Limited company (AS) Karmøy Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −17,000
Equity NOK 1.3m
Incorporated 2006
Share capital NOK 100,000

Signals

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

KOPERVIK KAPITALFORVALTNING AS is registered as a limited company in Karmøy, Rogaland with organisation number 990117705. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Kjøp og salg av aksjer, investering i fast eiendom, utleie, diverse konsulentoppdrag, samt delta i andre selskap.”.

Key figures · 2025

Operating profit
NOK −17,000
Equity
NOK 1.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns KOPERVIK KAPITALFORVALTNING AS?

ARVID VEDØY
KOPERVIK KAPITALFORVALTNING AS
· NOK −17,000 profit

KOPERVIK KAPITALFORVALTNING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does KOPERVIK KAPITALFORVALTNING AS own?

KOPERVIK KAPITALFORVALTNING AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about KOPERVIK KAPITALFORVALTNING AS

Who owns KOPERVIK KAPITALFORVALTNING AS?

ARVID VEDØY is the largest registered owner, with 100.0%.

Who is the general manager of KOPERVIK KAPITALFORVALTNING AS?

Arvid Vedøy is registered as general manager of KOPERVIK KAPITALFORVALTNING AS.

Where is KOPERVIK KAPITALFORVALTNING AS based?

KOPERVIK KAPITALFORVALTNING AS has its business address in Kopervik.

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.