BIZTRAC BETA
Rental and operating of own or leased real estate

ØVRE HOLEN EIENDOM AS

Org. no. 998410886 Limited company (AS) Øygarden Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 318,000
Operating profit NOK 257,000
Equity NOK 2.3m
Incorporated 2012
Share capital NOK 1.0m

ØVRE HOLEN EIENDOM AS is registered as a limited company in Øygarden, Vestland with organisation number 998410886. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2012. Registered share capital is NOK 1.0m, divided into 1000 shares. The company's stated purpose is: “Kjøp, drift og salg av fast eiendom og alt som står i forbindelse med dette, herunder deltakelse i annen virksomhet med likeartet formål.”. The most recent filed accounts, for the 2024 financial year, show NOK 318,000 in revenue and NOK 257,000 in operating profit.

Key figures · 2024

Revenue
NOK 318,000
Operating profit
NOK 257,000
Equity
NOK 2.3m
Est. value
NOK 2.1m

Financial health · 2024

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

Who owns ØVRE HOLEN EIENDOM AS?

DAG INGE YDDAL
ØVRE HOLEN EIENDOM AS
NOK 318,000 rev. · NOK 257,000 profit

ØVRE HOLEN EIENDOM AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ØVRE HOLEN EIENDOM AS

Who owns ØVRE HOLEN EIENDOM AS?

DAG INGE YDDAL is the largest registered owner, with 50.0%.

What is the revenue of ØVRE HOLEN EIENDOM AS?

ØVRE HOLEN EIENDOM AS had revenue of NOK 318,000 in 2024.

Who is the general manager of ØVRE HOLEN EIENDOM AS?

Dag Inge Yddal is registered as general manager of ØVRE HOLEN EIENDOM AS.

Where is ØVRE HOLEN EIENDOM AS based?

ØVRE HOLEN EIENDOM AS has its business address in Knarrevik.

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.