BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

OLSENS ØYE AS

Org. no. 988031399 Limited company (AS) Lillehammer Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 4.6m
Operating profit NOK 1.1m
Equity NOK 29.4m
Incorporated 2005
Share capital NOK 100,000

OLSENS ØYE AS is registered as a limited company in Lillehammer, Innlandet with organisation number 988031399. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2005. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av øyelegepraksis og annen operativ virksomhet, finansforvaltning og drift av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.6m in revenue and NOK 1.1m in operating profit.

Key figures · 2024

Revenue
NOK 4.6m
Operating profit
NOK 1.1m
Equity
NOK 29.4m
Est. value
NOK 23.5m

Financial health · 2024

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

Who owns OLSENS ØYE AS?

BIRGER ARE OLSEN
OLSENS ØYE AS
NOK 4.6m rev. · NOK 1.1m profit

OLSENS ØYE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does OLSENS ØYE AS own?

OLSENS ØYE AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about OLSENS ØYE AS

Who owns OLSENS ØYE AS?

BIRGER ARE OLSEN is the largest registered owner, with 100.0%.

What is the revenue of OLSENS ØYE AS?

OLSENS ØYE AS had revenue of NOK 4.6m in 2024.

Who is the general manager of OLSENS ØYE AS?

Birger Are Olsen is registered as general manager of OLSENS ØYE AS.

Where is OLSENS ØYE AS based?

OLSENS ØYE AS has its business address in Lillehammer.

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.