BIZTRAC BETA
COMPANY REGISTER PROFILE
996336271 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Other captive investment companies

HAUGSBU AS

Org. no. 996336271 Limited company (AS) Haugesund Incorporated 2010 Active
Ownership graph ↗
Operating profit NOK −12,000
Equity NOK 7.4m
Incorporated 2010
Share capital NOK 100,000

Signals

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

HAUGSBU AS is registered as a limited company in Haugesund, Rogaland with organisation number 996336271. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2010. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Investering i aksjer og andeler i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −12,000
▼ −9 %
Equity
NOK 7.4m
▲ +8 %
Est. value
NOK 6.1m

Financial health · 2025

Liquidity
115.53
Very good
Current assets ÷ current liabilities
Profitability
8.6%
Satisfactory
Return on total assets
Solidity
99.4%
Very good
Equity as a share of total capital

Who owns HAUGSBU AS?

HAUGSBU AS has 3 registered shareholders:

All shareholders and roles →

Which companies does HAUGSBU AS own?

HAUGSBU AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about HAUGSBU AS

Who owns HAUGSBU AS?

HILDE MARIT HAUGE is the largest registered owner, with 72.0%.

Where is HAUGSBU AS based?

HAUGSBU AS has its business address in Haugesund.

Property

Business address Svehaug 32, 5535 Haugesund
Cadastral unit 1106-35/620/0/0
Building Enebolig · 1 unit

The address this company is registered at, from the company register and matched against the cadastre. It does not say who owns the property — a company may be a tenant, and the address is often its accountant's. Source: Brønnøysundregistrene and © Kartverket.

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

Report a problem

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