BIZTRAC BETA
General medical practice activities

DOKTOR TYSNES AS

Org. no. 924393149 Limited company (AS) Bærum Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 3.8m
Operating profit NOK 1.3m
Equity NOK 79,000
Incorporated 2019
Share capital NOK 30,000

DOKTOR TYSNES AS is registered as a limited company in Bærum, Akershus with organisation number 924393149. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Legevirksomhet/drive allmennlegepraksis. Kjøp, utleie/drift og salg av eiendom og det som derved følger med. Videre kjøp/salg av aksjer og andre verdipapirer og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.8m in revenue and NOK 1.3m in operating profit.

Key figures · 2025

Revenue
NOK 3.8m
Operating profit
NOK 1.3m
Equity
NOK 79,000
Est. value
NOK 4.3m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns DOKTOR TYSNES AS?

KARIN NILSEN TYSNES
DOKTOR TYSNES AS
NOK 3.8m rev. · NOK 1.3m profit

DOKTOR TYSNES AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about DOKTOR TYSNES AS

Who owns DOKTOR TYSNES AS?

KARIN NILSEN TYSNES is the largest registered owner, with 100.0%.

What is the revenue of DOKTOR TYSNES AS?

DOKTOR TYSNES AS had revenue of NOK 3.8m in 2025.

Who is the general manager of DOKTOR TYSNES AS?

Karin Nilsen Tysnes is registered as general manager of DOKTOR TYSNES AS.

Where is DOKTOR TYSNES AS based?

DOKTOR TYSNES AS has its business address in Jar.

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.