BIZTRAC BETA
Business and other management consultancy activities

HIBA AS

Org. no. 988278009 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −213,000
Equity NOK 50.0m
Incorporated 2005
Share capital NOK 30,000

Signals

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

HIBA AS is registered as a limited company in Trondheim, Trøndelag with organisation number 988278009. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2005. Registered share capital is NOK 30,000, divided into 2400 shares. The company's stated purpose is: “Handels- og konsulentvirksomhet samt deltakelse som aksjonær eller på annen måte i foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −213,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −213,000
Equity
NOK 50.0m
Est. value
NOK 56.7m

Financial health · 2024

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

Who owns HIBA AS?

HEIDI IRENE BLENGSLI AABEL
HIBA AS
NOK 0 rev. · NOK −213,000 profit

HIBA AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HIBA AS own?

HIBA AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HIBA AS

Who owns HIBA AS?

HEIDI IRENE BLENGSLI AABEL is the largest registered owner, with 80.0%.

What is the revenue of HIBA AS?

HIBA AS had revenue of NOK 0 in 2024.

Who is the general manager of HIBA AS?

Heidi Irene Blengsli Aabel is registered as general manager of HIBA AS.

Where is HIBA AS based?

HIBA 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 15.06.2026.

Report a problem

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