BIZTRAC BETA
Development of building projects

HAREID RØR EIENDOM AS

Org. no. 918283161 Limited company (AS) Hareid Incorporated 1966 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −25,000
Equity NOK 2.6m
Incorporated 1966
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−25k kr).

HAREID RØR EIENDOM AS is registered as a limited company in Hareid, Møre og Romsdal with organisation number 918283161. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 1966. Registered share capital is NOK 100,000, divided into 20 shares. The company's stated purpose is: “Eie og leie ut fast eiendom, investere i aksjer, samt hva dermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −25,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −25,000
Equity
NOK 2.6m
Est. value
NOK 2.4m

Financial health · 2024

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

Who owns HAREID RØR EIENDOM AS?

ÅSE JOHANNE HOLSTAD HÅNES
HAREID RØR EIENDOM AS
NOK 0 rev. · NOK −25,000 profit

HAREID RØR EIENDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAREID RØR EIENDOM AS

Who owns HAREID RØR EIENDOM AS?

ÅSE JOHANNE HOLSTAD HÅNES is the largest registered owner, with 25.0%.

What is the revenue of HAREID RØR EIENDOM AS?

HAREID RØR EIENDOM AS had revenue of NOK 0 in 2024.

Who is the general manager of HAREID RØR EIENDOM AS?

Otto Håvard Holstad is registered as general manager of HAREID RØR EIENDOM AS.

Where is HAREID RØR EIENDOM AS based?

HAREID RØR EIENDOM 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.