BIZTRAC BETA
Rental and operating of own or leased real estate

HAVER EIENDOM AS

Org. no. 976388828 Limited company (AS) Incorporated 1996 Active
Ownership graph ↗
Revenue 2025 NOK 111,000
Operating profit NOK −13,000
Equity NOK −666,000
Incorporated 1996
Share capital NOK 100,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−666k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−13k kr).

HAVER EIENDOM AS is registered as a limited company in Hå, Rogaland with organisation number 976388828. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1996. Registered share capital is NOK 100,000, divided into 10 shares. The company's stated purpose is: “Eiendomsdrift og lignende.”. The most recent filed accounts, for the 2025 financial year, show NOK 111,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

Revenue
NOK 111,000
Operating profit
NOK −13,000
Equity
NOK −666,000

Financial health · 2025

Liquidity
0.80
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-221.4%
Weak
Equity as a share of total capital

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

Who owns HAVER EIENDOM AS?

ODD HAVER
HAVER EIENDOM AS
NOK 111,000 rev. · NOK −13,000 profit

HAVER EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HAVER EIENDOM AS

Who owns HAVER EIENDOM AS?

ODD HAVER is the largest registered owner, with 100.0%.

What is the revenue of HAVER EIENDOM AS?

HAVER EIENDOM AS had revenue of NOK 111,000 in 2025.

Who is the general manager of HAVER EIENDOM AS?

Odd Haver is registered as general manager of HAVER EIENDOM AS.

Where is HAVER EIENDOM AS based?

HAVER EIENDOM AS has its business address in Sirevåg.

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.