BIZTRAC BETA
Development of building projects

HOVDEN ALPIN INVEST AS

Org. no. 996770672 Limited company (AS) Bykle Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −62,000
Equity NOK −1.3m
Incorporated 2010
Share capital NOK 100,000

Signals

3 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,3 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−62k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HOVDEN ALPIN INVEST AS is registered as a limited company in Bykle, Agder with organisation number 996770672. The business is classified under development of building projects (NACE 68.120). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 10000 shares. The company's stated purpose is: “Eiendomsutvikling, samt hva hermed står i forbindelse, herunder deltagelse i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −62,000
Equity
NOK −1.3m

Financial health · 2024

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

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

Who owns HOVDEN ALPIN INVEST AS?

HAGEL INVEST AS
HOVDEN ALPIN INVEST AS
· NOK −62,000 profit

HOVDEN ALPIN INVEST AS has 8 registered shareholders:

All shareholders and roles →

Which companies does HOVDEN ALPIN INVEST AS own?

HOVDEN ALPIN INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOVDEN ALPIN INVEST AS

Who owns HOVDEN ALPIN INVEST AS?

HAGEL INVEST AS is the largest registered owner, with 40.8%.

Where is HOVDEN ALPIN INVEST AS based?

HOVDEN ALPIN INVEST AS has its business address in Hovden I Setesdal.

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.