BIZTRAC BETA
Retail sale of medical and orthopaedic goods

OPTIKER NELVIK ÅLESUND AS

Org. no. 980590682 Limited company (AS) Ålesund Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 10.1m
Operating profit NOK 1.1m
Equity NOK 997,000
Incorporated 1999
Employees 5
Share capital NOK 100,000

OPTIKER NELVIK ÅLESUND AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 980590682. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 1999 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å drive optikervirksomhet, og alt som hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 10.1m in revenue and NOK 1.1m in operating profit.

Key figures · 2025

Revenue
NOK 10.1m
Operating profit
NOK 1.1m
Equity
NOK 997,000
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns OPTIKER NELVIK ÅLESUND AS?

JOTHOSI HOLDING AS
OPTIKER NELVIK ÅLESUND AS
NOK 10.1m rev. · NOK 1.1m profit

OPTIKER NELVIK ÅLESUND AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPTIKER NELVIK ÅLESUND AS

Who owns OPTIKER NELVIK ÅLESUND AS?

JOTHOSI HOLDING AS is the largest registered owner, with 70.0%.

What is the revenue of OPTIKER NELVIK ÅLESUND AS?

OPTIKER NELVIK ÅLESUND AS had revenue of NOK 10.1m in 2025.

Who is the general manager of OPTIKER NELVIK ÅLESUND AS?

Thorkild Nelvik is registered as general manager of OPTIKER NELVIK ÅLESUND AS.

Where is OPTIKER NELVIK ÅLESUND AS based?

OPTIKER NELVIK ÅLESUND AS has its business address in Ålesund.

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.