BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

NESE KIRURGISK SENTER AS

Org. no. 912404854 Limited company (AS) Frogn Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 11.0m
Operating profit NOK 5.2m
Equity NOK 1.4m
Incorporated 2013
Share capital NOK 30,000

NESE KIRURGISK SENTER AS is registered as a limited company in Frogn, Akershus with organisation number 912404854. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Legevirksomhet med spesialisering innenfor øre, nese og hals.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.0m in revenue and NOK 5.2m in operating profit.

Key figures · 2024

Revenue
NOK 11.0m
Operating profit
NOK 5.2m
Equity
NOK 1.4m
Est. value
NOK 18.1m

Financial health · 2024

Liquidity
1.11
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
22.8%
Good
Equity as a share of total capital

Who owns NESE KIRURGISK SENTER AS?

ØYSTEIN SHAHIN ESKELAND
NESE KIRURGISK SENTER AS
NOK 11.0m rev. · NOK 5.2m profit

NESE KIRURGISK SENTER AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NESE KIRURGISK SENTER AS

Who owns NESE KIRURGISK SENTER AS?

ØYSTEIN SHAHIN ESKELAND is the largest registered owner, with 100.0%.

What is the revenue of NESE KIRURGISK SENTER AS?

NESE KIRURGISK SENTER AS had revenue of NOK 11.0m in 2024.

Who is the general manager of NESE KIRURGISK SENTER AS?

Øystein Shahin Eskeland is registered as general manager of NESE KIRURGISK SENTER AS.

Where is NESE KIRURGISK SENTER AS based?

NESE KIRURGISK SENTER AS has its business address in Drøbak.

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.