BIZTRAC BETA
Uoppgitt

HEINE HUSDAL INVEST AS

Org. no. 930225177 Limited company (AS) Stavanger Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −8,000
Equity NOK 78,000
Incorporated 2022
Share capital NOK 50,000

Signals

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

HEINE HUSDAL INVEST AS is registered as a limited company in Stavanger, Rogaland with organisation number 930225177. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Investering i aksjer, verdipapirer og andre investeringsobjekter.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −8,000
Equity
NOK 78,000
Est. value
NOK 92,000

Financial health · 2024

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

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

Who owns HEINE HUSDAL INVEST AS?

HEINE ELIAS HUSDAL
HEINE HUSDAL INVEST AS
NOK 0 rev. · NOK −8,000 profit

HEINE HUSDAL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HEINE HUSDAL INVEST AS own?

HEINE HUSDAL INVEST AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HEINE HUSDAL INVEST AS

Who owns HEINE HUSDAL INVEST AS?

HEINE ELIAS HUSDAL is the largest registered owner, with 100.0%.

What is the revenue of HEINE HUSDAL INVEST AS?

HEINE HUSDAL INVEST AS had revenue of NOK 0 in 2024.

Where is HEINE HUSDAL INVEST AS based?

HEINE HUSDAL INVEST AS has its business address in Stavanger.

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.