BIZTRAC BETA
General medical practice activities

DR ØSTHUS AS

Org. no. 914755786 Limited company (AS) Randaberg Incorporated 2014 Active
Ownership graph ↗
Revenue 2024 NOK 5.6m
Operating profit NOK 2.8m
Equity NOK 10.2m
Incorporated 2014
Employees 5
Share capital NOK 30,000

DR ØSTHUS AS is registered as a limited company in Randaberg, Rogaland with organisation number 914755786. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2014 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Legevirksomhet. Videre kjøp/salg og drift av fast eiendom, kjøp/salg av aksjer og andre verdipapirer og hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.6m in revenue and NOK 2.8m in operating profit.

Key figures · 2024

Revenue
NOK 5.6m
Operating profit
NOK 2.8m
Equity
NOK 10.2m
Est. value
NOK 17.7m

Financial health · 2024

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

Who owns DR ØSTHUS AS?

DAG RUNE ØSTHUS
DR ØSTHUS AS
NOK 5.6m rev. · NOK 2.8m profit

DR ØSTHUS AS has 1 registered shareholder:

All shareholders and roles →

Which companies does DR ØSTHUS AS own?

DR ØSTHUS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about DR ØSTHUS AS

Who owns DR ØSTHUS AS?

DAG RUNE ØSTHUS is the largest registered owner, with 100.0%.

What is the revenue of DR ØSTHUS AS?

DR ØSTHUS AS had revenue of NOK 5.6m in 2024.

Who is the general manager of DR ØSTHUS AS?

Dag Rune Østhus is registered as general manager of DR ØSTHUS AS.

Where is DR ØSTHUS AS based?

DR ØSTHUS AS has its business address in Randaberg.

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.