biztrac. BETA
COMPANY REGISTER PROFILE
926051911 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Computer programming activities

HÅLU AS

Org. no. 926051911 Limited company (AS) Trondheim Incorporated 2020 Active
Revenue 2025 NOK 0
Operating profit NOK −3,000
Equity NOK 13,000
Incorporated 2020
Share capital NOK 30,000

Signals

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

HÅLU AS is registered as a limited company in Trondheim, Trøndelag with organisation number 926051911. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Holdingselskap”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −3,000
▲ +78 %
Equity
NOK 13,000
▼ −19 %
Est. value
NOK 24,000

Financial health · 2025

Liquidity
1.14
Satisfactory
Current assets ÷ current liabilities
Profitability
-3.2%
Not satisfactory
Return on total assets
Solidity
13.9%
Weak
Equity as a share of total capital

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

Who owns HÅLU AS?

HÅLU AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HÅLU AS own?

HÅLU AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

HÅLU AS er morselskap for 1 datterselskap:

Frequently asked questions about HÅLU AS

Who owns HÅLU AS?

Lucia De La Sierra Seco is the largest registered owner, with 50.0%.

What is the revenue of HÅLU AS?

HÅLU AS had revenue of NOK 0 in 2025.

Who is the general manager of HÅLU AS?

Håkon Hesselberg Hålu is registered as general manager of HÅLU AS.

Where is HÅLU AS based?

HÅLU AS has its business address in Trondheim.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.