BIZTRAC BETA
Rental and operating of own or leased real estate

HÅLI HOLDING AS

Org. no. 989168312 Limited company (AS) Vefsn Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 1.0m
Operating profit NOK −353,000
Equity NOK 62.4m
Incorporated 2005
Share capital NOK 61,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−353k kr).

HÅLI HOLDING AS is registered as a limited company in Vefsn, Nordland with organisation number 989168312. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2005. Registered share capital is NOK 61,000, divided into 202 shares. The company's stated purpose is: “Investering i aksjer, fast eiendom mv.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.0m in revenue and NOK −353,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.0m
Operating profit
NOK −353,000
Equity
NOK 62.4m
Est. value
NOK 45.0m

Financial health · 2025

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

Who owns HÅLI HOLDING AS?

STEIN HAUGE
HÅLI HOLDING AS
NOK 1.0m rev. · NOK −353,000 profit

HÅLI HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HÅLI HOLDING AS own?

HÅLI HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about HÅLI HOLDING AS

Who owns HÅLI HOLDING AS?

STEIN HAUGE is the largest registered owner, with 50.0%.

What is the revenue of HÅLI HOLDING AS?

HÅLI HOLDING AS had revenue of NOK 1.0m in 2025.

Who is the general manager of HÅLI HOLDING AS?

Tone Helen Hauge is registered as general manager of HÅLI HOLDING AS.

Where is HÅLI HOLDING AS based?

HÅLI HOLDING AS has its business address in Mosjøen.

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.