BIZTRAC BETA
Retail sale of medical and orthopaedic goods

STRAEN OPTISKE AS

Org. no. 990201390 Limited company (AS) Stavanger Incorporated 2006 Active
Ownership graph ↗
Revenue 2024 NOK 8.6m
Operating profit NOK 1.1m
Equity NOK 487,000
Incorporated 2006
Employees 7
Share capital NOK 90,000

STRAEN OPTISKE AS is registered as a limited company in Stavanger, Rogaland with organisation number 990201390. The business is classified under retail sale of medical and orthopaedic goods (NACE 47.740). The company was incorporated in 2006 and has 7 registered employees. Registered share capital is NOK 90,000, divided into 600 shares. The company's stated purpose is: “Optikervirksomhet og hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 8.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 8.6m
Operating profit
NOK 1.1m
Equity
NOK 487,000
Est. value
NOK 3.7m

Financial health · 2024

Liquidity
1.19
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
16.6%
Satisfactory
Equity as a share of total capital

Who owns STRAEN OPTISKE AS?

EIVIND EGELAND
STRAEN OPTISKE AS
NOK 8.6m rev. · NOK 1.1m profit

STRAEN OPTISKE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does STRAEN OPTISKE AS own?

STRAEN OPTISKE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about STRAEN OPTISKE AS

Who owns STRAEN OPTISKE AS?

EIVIND EGELAND is the largest registered owner, with 50.0%.

What is the revenue of STRAEN OPTISKE AS?

STRAEN OPTISKE AS had revenue of NOK 8.6m in 2024.

Who is the general manager of STRAEN OPTISKE AS?

Eivind Egeland is registered as general manager of STRAEN OPTISKE AS.

Where is STRAEN OPTISKE AS based?

STRAEN OPTISKE AS has its business address in Stavanger.

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.