BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ØYELEGE DR. MEIKE SPORBECK AS

Org. no. 825541462 Limited company (AS) Stavanger Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 8.9m
Operating profit NOK 886,000
Equity NOK 1.5m
Incorporated 2020
Share capital NOK 30,000

ØYELEGE DR. MEIKE SPORBECK AS is registered as a limited company in Stavanger, Rogaland with organisation number 825541462. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Øyelegetjenester.”. The most recent filed accounts, for the 2025 financial year, show NOK 8.9m in revenue and NOK 886,000 in operating profit.

Key figures · 2025

Revenue
NOK 8.9m
Operating profit
NOK 886,000
Equity
NOK 1.5m
Est. value
NOK 5.2m

Financial health · 2025

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

Who owns ØYELEGE DR. MEIKE SPORBECK AS?

MEIKE SPORBECK
ØYELEGE DR. MEIKE SPORBECK AS
NOK 8.9m rev. · NOK 886,000 profit

ØYELEGE DR. MEIKE SPORBECK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ØYELEGE DR. MEIKE SPORBECK AS own?

ØYELEGE DR. MEIKE SPORBECK AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ØYELEGE DR. MEIKE SPORBECK AS

Who owns ØYELEGE DR. MEIKE SPORBECK AS?

MEIKE SPORBECK is the largest registered owner, with 100.0%.

What is the revenue of ØYELEGE DR. MEIKE SPORBECK AS?

ØYELEGE DR. MEIKE SPORBECK AS had revenue of NOK 8.9m in 2025.

Where is ØYELEGE DR. MEIKE SPORBECK AS based?

ØYELEGE DR. MEIKE SPORBECK 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.