BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

ØYELEGE ECKHOFF AS

Org. no. 923177639 Limited company (AS) Kristiansand Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 7.3m
Operating profit NOK 1.4m
Equity NOK 124,000
Incorporated 2019
Share capital NOK 30,000

ØYELEGE ECKHOFF AS is registered as a limited company in Kristiansand, Agder with organisation number 923177639. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Øyelegepraksis, samt alt hva hermed står i forbindelse. Selskapet kan gjennom aksjetegning eller på annen måte delta i andre selskap eller foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.3m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 7.3m
Operating profit
NOK 1.4m
Equity
NOK 124,000
Est. value
NOK 5.2m

Financial health · 2024

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

Who owns ØYELEGE ECKHOFF AS?

MOEN ECKHOFF HOLDING AS
ØYELEGE ECKHOFF AS
NOK 7.3m rev. · NOK 1.4m profit

ØYELEGE ECKHOFF AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØYELEGE ECKHOFF AS

Who owns ØYELEGE ECKHOFF AS?

MOEN ECKHOFF HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØYELEGE ECKHOFF AS?

ØYELEGE ECKHOFF AS had revenue of NOK 7.3m in 2024.

Who is the general manager of ØYELEGE ECKHOFF AS?

Edvard Moen Eckhoff is registered as general manager of ØYELEGE ECKHOFF AS.

Where is ØYELEGE ECKHOFF AS based?

ØYELEGE ECKHOFF AS has its business address in Kristiansand S.

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.