BIZTRAC BETA
Retail sale of medical and orthopaedic goods

STORGATA OPTISKE A/S

Org. no. 812977822 Limited company (AS) Jevnaker Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 3.3m
Operating profit NOK 339,000
Equity NOK 1.1m
Incorporated 2013
Share capital NOK 30,000

STORGATA OPTISKE A/S is registered as a limited company in Jevnaker, Akershus with organisation number 812977822. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Synsundersøkelser og butikkhandel med optiske artikler og ur.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.3m in revenue and NOK 339,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.3m
Operating profit
NOK 339,000
Equity
NOK 1.1m
Est. value
NOK 1.8m

Financial health · 2025

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

Who owns STORGATA OPTISKE A/S?

SOLVEIG HAUGEN
STORGATA OPTISKE A/S
NOK 3.3m rev. · NOK 339,000 profit

STORGATA OPTISKE A/S has 2 registered shareholders:

All shareholders and roles →

Which companies does STORGATA OPTISKE A/S own?

STORGATA OPTISKE A/S holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STORGATA OPTISKE A/S

Who owns STORGATA OPTISKE A/S?

SOLVEIG HAUGEN is the largest registered owner, with 50.0%.

What is the revenue of STORGATA OPTISKE A/S?

STORGATA OPTISKE A/S had revenue of NOK 3.3m in 2025.

Who is the general manager of STORGATA OPTISKE A/S?

Håkon Haugen is registered as general manager of STORGATA OPTISKE A/S.

Where is STORGATA OPTISKE A/S based?

STORGATA OPTISKE A/S has its business address in Jevnaker.

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.