BIZTRAC BETA
COMPANY REGISTER PROFILE
960705432 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 02.09.2026
Hotels and similar accommodation

ØREN EIENDOM AS

Org. no. 960705432 Limited company (AS) Høyanger Incorporated 1991 Active
Ownership graph ↗
Revenue 2025 NOK 1.5m
Operating profit NOK 448,000
Equity NOK 5.9m
Incorporated 1991
Share capital NOK 2.3m

ØREN EIENDOM AS is registered as a limited company in Høyanger, Vestland with organisation number 960705432. The business is classified under hotels and similar accommodation (NACE 55.100). The company was incorporated in 1991. Registered share capital is NOK 2.3m. The company's stated purpose is: “Planlegge, bygge, leige ut og drive forretnings- og kontorbygg samt anna verksemd som naturleg fell inn under dette ved aksjekjøp eller på anna måte.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.5m in revenue and NOK 448,000 in operating profit.

Former names: HØYANGER EIGEDOMSSELSKAP AS

Key figures · 2025

Revenue
NOK 1.5m
▼ −35 %
Operating profit
NOK 448,000
▼ −73 %
Equity
NOK 5.9m
▲ +3 %
Est. value
NOK 5.3m

Financial health · 2025

Liquidity
0.36
Not satisfactory
Current assets ÷ current liabilities
Profitability
4.9%
Weak
Return on total assets
Solidity
49.1%
Very good
Equity as a share of total capital

Who owns ØREN EIENDOM AS?

ØREN EIENDOM AS
NOK 1.5m rev. · NOK 448,000 profit

ØREN EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ØREN EIENDOM AS

Who owns ØREN EIENDOM AS?

HØYANGER TRELAST HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of ØREN EIENDOM AS?

ØREN EIENDOM AS had revenue of NOK 1.5m in 2025.

Who is the general manager of ØREN EIENDOM AS?

Frode Øren is registered as general manager of ØREN EIENDOM AS.

Where is ØREN EIENDOM AS based?

ØREN EIENDOM AS has its business address in Høyanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.