BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

HUDLEGE SHEILA FEVANG AS

Org. no. 929336399 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 6.5m
Operating profit NOK 2.6m
Equity NOK 4.9m
Incorporated 2022
Employees 5
Share capital NOK 30,000

HUDLEGE SHEILA FEVANG AS is registered as a limited company in Stavanger, Rogaland with organisation number 929336399. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2022 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Legevirksomhet med spesialfelt som hudlege.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.5m in revenue and NOK 2.6m in operating profit.

Key figures · 2025

Revenue
NOK 6.5m
Operating profit
NOK 2.6m
Equity
NOK 4.9m
Est. value
NOK 12.5m

Financial health · 2025

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

Who owns HUDLEGE SHEILA FEVANG AS?

SHEILA ANN MILLS FEVANG
HUDLEGE SHEILA FEVANG AS
NOK 6.5m rev. · NOK 2.6m profit

HUDLEGE SHEILA FEVANG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HUDLEGE SHEILA FEVANG AS

Who owns HUDLEGE SHEILA FEVANG AS?

SHEILA ANN MILLS FEVANG is the largest registered owner, with 100.0%.

What is the revenue of HUDLEGE SHEILA FEVANG AS?

HUDLEGE SHEILA FEVANG AS had revenue of NOK 6.5m in 2025.

Who is the general manager of HUDLEGE SHEILA FEVANG AS?

Sheila Ann Mills Fevang is registered as general manager of HUDLEGE SHEILA FEVANG AS.

Where is HUDLEGE SHEILA FEVANG AS based?

HUDLEGE SHEILA FEVANG 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.