BIZTRAC BETA
General medical practice activities

HISØY LEGESENTER EIENDOM AS

Org. no. 980919420 Limited company (AS) Arendal Incorporated 1999 Active
Ownership graph ↗
Revenue 2025 NOK 1.8m
Operating profit NOK 1.4m
Equity NOK 1.6m
Incorporated 1999
Share capital NOK 105,000

HISØY LEGESENTER EIENDOM AS is registered as a limited company in Arendal, Agder with organisation number 980919420. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 1999. Registered share capital is NOK 105,000, divided into 2100 shares. The company's stated purpose is: “Eie og forvalte eiendom. Selskapet kan også delta i andre selskaper og foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.8m in revenue and NOK 1.4m in operating profit.

Key figures · 2025

Revenue
NOK 1.8m
Operating profit
NOK 1.4m
Equity
NOK 1.6m
Est. value
NOK 5.5m

Financial health · 2025

Liquidity
1.28
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
30.5%
Good
Equity as a share of total capital

Who owns HISØY LEGESENTER EIENDOM AS?

LEGE VESLEMØY HIPPE AS
HISØY LEGESENTER EIENDOM AS
NOK 1.8m rev. · NOK 1.4m profit

HISØY LEGESENTER EIENDOM AS has 5 registered shareholders:

All shareholders and roles →

Frequently asked questions about HISØY LEGESENTER EIENDOM AS

Who owns HISØY LEGESENTER EIENDOM AS?

LEGE VESLEMØY HIPPE AS is the largest registered owner, with 20.0%.

What is the revenue of HISØY LEGESENTER EIENDOM AS?

HISØY LEGESENTER EIENDOM AS had revenue of NOK 1.8m in 2025.

Who is the general manager of HISØY LEGESENTER EIENDOM AS?

Dag Johannes Nordhaug is registered as general manager of HISØY LEGESENTER EIENDOM AS.

Where is HISØY LEGESENTER EIENDOM AS based?

HISØY LEGESENTER EIENDOM AS has its business address in Kolbjørnsvik.

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.