BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

AGRO ØRE-NESE-HALSKLINIKK AS

Org. no. 897104962 Limited company (AS) Asker Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 6.7m
Operating profit NOK 81,000
Equity NOK 743,000
Incorporated 2011
Employees 5
Share capital NOK 100,000

AGRO ØRE-NESE-HALSKLINIKK AS is registered as a limited company in Asker, Akershus with organisation number 897104962. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2011 and has 5 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Legevirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.7m in revenue and NOK 81,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.7m
Operating profit
NOK 81,000
Equity
NOK 743,000
Est. value
NOK 929,000

Financial health · 2024

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

Who owns AGRO ØRE-NESE-HALSKLINIKK AS?

DR. ROARSEN AS
AGRO ØRE-NESE-HALSKLINIKK AS
NOK 6.7m rev. · NOK 81,000 profit

AGRO ØRE-NESE-HALSKLINIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AGRO ØRE-NESE-HALSKLINIKK AS

Who owns AGRO ØRE-NESE-HALSKLINIKK AS?

DR. ROARSEN AS is the largest registered owner, with 100.0%.

What is the revenue of AGRO ØRE-NESE-HALSKLINIKK AS?

AGRO ØRE-NESE-HALSKLINIKK AS had revenue of NOK 6.7m in 2024.

Who is the general manager of AGRO ØRE-NESE-HALSKLINIKK AS?

Robby Roarsen is registered as general manager of AGRO ØRE-NESE-HALSKLINIKK AS.

Where is AGRO ØRE-NESE-HALSKLINIKK AS based?

AGRO ØRE-NESE-HALSKLINIKK AS has its business address in Asker.

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.