BIZTRAC BETA
General medical practice activities

DR. FAGERNÆS AS

Org. no. 930686271 Limited company (AS) Larvik Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3.5m
Operating profit NOK 240,000
Equity NOK 1.1m
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-02-16 Adresseendring registrert 2026-02-16.

DR. FAGERNÆS AS is registered as a limited company in Larvik, Vestfold with organisation number 930686271. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skal selge tjenester og varer innen fastlegevirksomhet, og annet som naturlig sammenfaller med dette, samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.5m in revenue and NOK 240,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.5m
Operating profit
NOK 240,000
Equity
NOK 1.1m
Est. value
NOK 1.9m

Financial health · 2025

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

Who owns DR. FAGERNÆS AS?

ØYSTEIN KOBRO FAGERNÆS
DR. FAGERNÆS AS
NOK 3.5m rev. · NOK 240,000 profit

DR. FAGERNÆS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DR. FAGERNÆS AS

Who owns DR. FAGERNÆS AS?

ØYSTEIN KOBRO FAGERNÆS is the largest registered owner, with 100.0%.

What is the revenue of DR. FAGERNÆS AS?

DR. FAGERNÆS AS had revenue of NOK 3.5m in 2025.

Who is the general manager of DR. FAGERNÆS AS?

Øystein Kobro Fagernæs is registered as general manager of DR. FAGERNÆS AS.

Where is DR. FAGERNÆS AS based?

DR. FAGERNÆS AS has its business address in Stavern.

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.