BIZTRAC BETA
Rental and operating of own or leased real estate

EH EIGEDOM AS

Org. no. 954962598 Limited company (AS) Voss Incorporated 1989 Active
Ownership graph ↗
Revenue 2024 NOK 36,000
Operating profit NOK −123,000
Equity NOK 4.8m
Incorporated 1989
Share capital NOK 100,000

Signals

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

EH EIGEDOM AS is registered as a limited company in Voss, Vestland with organisation number 954962598. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 1989. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Å eiga, forvalta og leiga ut fast eigedom. Selskapet kan også gjennom aksjekjøp eller på andre måtar engasjera seg i andre føretak uansett føremål og selskapsform.”. The most recent filed accounts, for the 2024 financial year, show NOK 36,000 in revenue and NOK −123,000 in operating profit.

Key figures · 2024

Revenue
NOK 36,000
Operating profit
NOK −123,000
Equity
NOK 4.8m
Est. value
NOK 3.3m

Financial health · 2024

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

Who owns EH EIGEDOM AS?

EDVIN HAUGSBØ
EH EIGEDOM AS
NOK 36,000 rev. · NOK −123,000 profit

EH EIGEDOM AS has 4 registered shareholders:

All shareholders and roles →

Which companies does EH EIGEDOM AS own?

EH EIGEDOM AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about EH EIGEDOM AS

Who owns EH EIGEDOM AS?

EDVIN HAUGSBØ is the largest registered owner, with 80.0%.

What is the revenue of EH EIGEDOM AS?

EH EIGEDOM AS had revenue of NOK 36,000 in 2024.

Where is EH EIGEDOM AS based?

EH EIGEDOM AS has its business address in Voss.

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.