biztrac. BETA
COMPANY REGISTER PROFILE
880959492 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Rental and operating of own or leased real estate

HARDANGER EIGEDOM AS

Org. no. 880959492 Limited company (AS) Ullensvang Incorporated 1999 Active
Revenue 2025 NOK 891,000
Operating profit NOK 536,000
Equity NOK 4.5m
Incorporated 1999
Share capital NOK 500,000

HARDANGER EIGEDOM AS is registered as a limited company in Ullensvang, Vestland with organisation number 880959492. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1999. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Drive eiendomsutvikling samt å delta i andre selskap eller foretak med lignende formål, og alt hva som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 891,000 in revenue and NOK 536,000 in operating profit.

Key figures · 2025

Revenue
NOK 891,000
▲ +2 %
Operating profit
NOK 536,000
▼ −6 %
Equity
NOK 4.5m
▲ +10 %
Est. value
NOK 4.4m

Financial health · 2025

Liquidity
4.39
Very good
Current assets ÷ current liabilities
Profitability
11.3%
Good
Return on total assets
Solidity
74.9%
Very good
Equity as a share of total capital

Who owns HARDANGER EIGEDOM AS?

HARDANGER EIGEDOM AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about HARDANGER EIGEDOM AS

Who owns HARDANGER EIGEDOM AS?

GARBERG AS is the largest registered owner, with 50.4%.

What is the revenue of HARDANGER EIGEDOM AS?

HARDANGER EIGEDOM AS had revenue of NOK 891,000 in 2025.

Who is the general manager of HARDANGER EIGEDOM AS?

Svein Petter Garberg is registered as general manager of HARDANGER EIGEDOM AS.

Where is HARDANGER EIGEDOM AS based?

HARDANGER EIGEDOM AS has its business address in Odda.

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

Report a problem

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