BIZTRAC BETA
Construction of residential and non-residential buildings

HASO HOLDING AS

Org. no. 991016651 Limited company (AS) Heim Incorporated 2007 Active
Ownership graph ↗
Operating profit NOK −164,000
Equity NOK 10.0m
Incorporated 2007
Share capital NOK 400,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−164k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

HASO HOLDING AS is registered as a limited company in Heim, Trøndelag with organisation number 991016651. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2007. Registered share capital is NOK 400,000, divided into 800 shares. The company's stated purpose is: “Kjøp og forvaltning av andre selskaper og alt som står i forbindelse med dette. Handelsvirksomhet, kjøp av aksjer i andre selskaper samt å delta i andre selskaper med lignende virksomhet.”.

Key figures · 2024

Operating profit
NOK −164,000
Equity
NOK 10.0m
Est. value
NOK 21.9m

Financial health · 2024

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

Who owns HASO HOLDING AS?

EMIL SOLBERG
HASO HOLDING AS
· NOK −164,000 profit

HASO HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does HASO HOLDING AS own?

HASO HOLDING AS holds stakes in 3 companies:

See the full ownership structure →

Group structure

HASO HOLDING AS er morselskap for 2 datterselskaper:

Frequently asked questions about HASO HOLDING AS

Who owns HASO HOLDING AS?

EMIL SOLBERG is the largest registered owner, with 30.0%.

Where is HASO HOLDING AS based?

HASO HOLDING AS has its business address in Kyrksæterøra.

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.