BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

HAV OG HELSE AS

Org. no. 934984064 Limited company (AS) Hareid Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 752,000
Operating profit NOK 23,000
Equity NOK 41,000
Incorporated 2025
Share capital NOK 30,000

HAV OG HELSE AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 934984064. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Legetjenester, konsulentvirksomhet og investering og deltakelse i eiendom og andre selskaper, samt alt som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 752,000 in revenue and NOK 23,000 in operating profit.

Key figures · 2025

Revenue
NOK 752,000
Operating profit
NOK 23,000
Equity
NOK 41,000
Est. value
NOK 130,000

Financial health · 2025

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

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

Who owns HAV OG HELSE AS?

ØRJAN YRI
HAV OG HELSE AS
NOK 752,000 rev. · NOK 23,000 profit

HAV OG HELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAV OG HELSE AS

Who owns HAV OG HELSE AS?

ØRJAN YRI is the largest registered owner, with 100.0%.

What is the revenue of HAV OG HELSE AS?

HAV OG HELSE AS had revenue of NOK 752,000 in 2025.

Who is the general manager of HAV OG HELSE AS?

Ørjan Yri is registered as general manager of HAV OG HELSE AS.

Where is HAV OG HELSE AS based?

HAV OG HELSE AS has its business address in Hareid.

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.