BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ØYELEGE J.R. EKSTRAND AS

Org. no. 989988670 Limited company (AS) Sarpsborg Incorporated 2006 Active
Ownership graph ↗
Revenue 2025 NOK 11.4m
Operating profit NOK 5.5m
Equity NOK 383,000
Incorporated 2006
Share capital NOK 100,000

ØYELEGE J.R. EKSTRAND AS is registered as a limited company in Sarpsborg, Østfold with organisation number 989988670. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2006. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Drift av spesialistpraksis (legevirksomhet) og alt som måtte stå i den forbindelse. ”. The most recent filed accounts, for the 2025 financial year, show NOK 11.4m in revenue and NOK 5.5m in operating profit.

Key figures · 2025

Revenue
NOK 11.4m
Operating profit
NOK 5.5m
Equity
NOK 383,000
Est. value
NOK 18.1m

Financial health · 2025

Liquidity
0.97
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
5.4%
Weak
Equity as a share of total capital

Who owns ØYELEGE J.R. EKSTRAND AS?

JULIAN RAFFAEL EKSTRAND
ØYELEGE J.R. EKSTRAND AS
NOK 11.4m rev. · NOK 5.5m profit

ØYELEGE J.R. EKSTRAND AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYELEGE J.R. EKSTRAND AS

Who owns ØYELEGE J.R. EKSTRAND AS?

JULIAN RAFFAEL EKSTRAND is the largest registered owner, with 100.0%.

What is the revenue of ØYELEGE J.R. EKSTRAND AS?

ØYELEGE J.R. EKSTRAND AS had revenue of NOK 11.4m in 2025.

Who is the general manager of ØYELEGE J.R. EKSTRAND AS?

Julian Raffael Ekstrand is registered as general manager of ØYELEGE J.R. EKSTRAND AS.

Where is ØYELEGE J.R. EKSTRAND AS based?

ØYELEGE J.R. EKSTRAND AS has its business address in Sarpsborg.

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.