BIZTRAC BETA
Wholesale of electrical household appliances

C OPTIKK AS

Org. no. 889257512 Limited company (AS) Kongsberg Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 43.2m
Operating profit NOK 5.2m
Equity NOK 3.0m
Incorporated 2005
Employees 6
Share capital NOK 183,000

C OPTIKK AS is registered as a limited company in Kongsberg, Buskerud with organisation number 889257512. The business is classified under wholesale of electrical household appliances (NACE 46.430). The company was incorporated in 2005 and has 6 registered employees. Registered share capital is NOK 183,000, divided into 183000 shares. The company's stated purpose is: “Handel og kjededrift i optisk bransje med alt som naturlig hører med, eie aksjer i andre selskaper, kjøp og salg av aksjer og andre verdipapirer, kjøp, salg og utleie av fast eiendom samt annen virksomhet som står i nær sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 43.2m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 43.2m
Operating profit
NOK 5.2m
Equity
NOK 3.0m
Est. value
NOK 16.9m

Financial health · 2024

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

Who owns C OPTIKK AS?

OLAV DALANE VIKESDAL
C OPTIKK AS
NOK 43.2m rev. · NOK 5.2m profit

C OPTIKK AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about C OPTIKK AS

Who owns C OPTIKK AS?

OLAV DALANE VIKESDAL is the largest registered owner, with 5.5%.

What is the revenue of C OPTIKK AS?

C OPTIKK AS had revenue of NOK 43.2m in 2024.

Who is the general manager of C OPTIKK AS?

Olav Dalane Vikesdal is registered as general manager of C OPTIKK AS.

Where is C OPTIKK AS based?

C OPTIKK AS has its business address in Kongsberg.

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.