BIZTRAC BETA
Other captive investment companies

HABBAS INVEST AS

Org. no. 916370067 Limited company (AS) Gjesdal Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −11,000
Equity NOK 183,000
Incorporated 2015
Share capital NOK 2.5m

Signals

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

HABBAS INVEST AS is registered as a limited company in Gjesdal, Rogaland with organisation number 916370067. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2015. Registered share capital is NOK 2.5m, divided into 25000 shares. The company's stated purpose is: “Investering i andre selskap og annet som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −11,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −11,000
Equity
NOK 183,000
Est. value
NOK 167,000

Financial health · 2024

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

Who owns HABBAS INVEST AS?

ENZO AS
HABBAS INVEST AS
NOK 0 rev. · NOK −11,000 profit

HABBAS INVEST AS has 10 registered shareholders:

All shareholders and roles →

Which companies does HABBAS INVEST AS own?

HABBAS INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HABBAS INVEST AS

Who owns HABBAS INVEST AS?

ENZO AS is the largest registered owner, with 20.0%.

What is the revenue of HABBAS INVEST AS?

HABBAS INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of HABBAS INVEST AS?

Hans Knut Stakkestad is registered as general manager of HABBAS INVEST AS.

Where is HABBAS INVEST AS based?

HABBAS INVEST AS has its business address in Ålgård.

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.