BIZTRAC BETA
Rental and leasing of other machinery, equipment and tangible goods n.e.c.

VIKAR OPTIKK AS

Org. no. 989862782 Limited company (AS) Nittedal Incorporated 2006 Active
Ownership graph ↗
Operating profit NOK −23,000
Equity NOK 3.0m
Incorporated 2006
Share capital NOK 100,000

Signals

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

VIKAR OPTIKK AS is registered as a limited company in Nittedal, Akershus with organisation number 989862782. The business is classified under rental and leasing of other machinery, equipment and tangible goods n.e.c. (NACE 77.390). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Utleie av arbeidskraft og konsulentvirksomhet innenfor den optiske bransje, deltagelse i andre virksomheter samt andre tjenester som står i forbindelse med dette. Kjøp, salg og utleie av fast eiendom.Kjøp,salg og utleie av campingbil og fritidsutstyr.”.

Key figures · 2025

Operating profit
NOK −23,000
Equity
NOK 3.0m
Est. value
NOK 1.7m

Financial health · 2025

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

Who owns VIKAR OPTIKK AS?

ØYSTEIN AAMODT
VIKAR OPTIKK AS
· NOK −23,000 profit

VIKAR OPTIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIKAR OPTIKK AS own?

VIKAR OPTIKK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIKAR OPTIKK AS

Who owns VIKAR OPTIKK AS?

ØYSTEIN AAMODT is the largest registered owner, with 100.0%.

Who is the general manager of VIKAR OPTIKK AS?

Øystein Aamodt is registered as general manager of VIKAR OPTIKK AS.

Where is VIKAR OPTIKK AS based?

VIKAR OPTIKK AS has its business address in Hagan.

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.