BIZTRAC BETA
Buying and selling of own real estate

HORNINDAL EIGEDOMSUTVIKLING HOLDING AS

Org. no. 919404140 Limited company (AS) Volda Incorporated 2017 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 557,000
Incorporated 2017
Share capital NOK 45,000

Signals

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

HORNINDAL EIGEDOMSUTVIKLING HOLDING AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 919404140. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2017. Registered share capital is NOK 45,000, divided into 10 shares. The company's stated purpose is: “Investeringsselskap, herunder å investere i aksjer, obligasjoner, fast eiendom, andeler i selskap etter selskapsloven og annet som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −9,000
Equity
NOK 557,000
Est. value
NOK 508,000

Financial health · 2024

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

Who owns HORNINDAL EIGEDOMSUTVIKLING HOLDING AS?

BOTTOLF GRODÅS
HORNINDAL EIGEDOMSUTVIKLING HOLDING AS
· NOK −9,000 profit

HORNINDAL EIGEDOMSUTVIKLING HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HORNINDAL EIGEDOMSUTVIKLING HOLDING AS own?

HORNINDAL EIGEDOMSUTVIKLING HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HORNINDAL EIGEDOMSUTVIKLING HOLDING AS

Who owns HORNINDAL EIGEDOMSUTVIKLING HOLDING AS?

BOTTOLF GRODÅS is the largest registered owner, with 100.0%.

Where is HORNINDAL EIGEDOMSUTVIKLING HOLDING AS based?

HORNINDAL EIGEDOMSUTVIKLING HOLDING AS has its business address in Hornindal.

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.