BIZTRAC BETA
Other captive investment companies

HAUGER HOLDING AS

Org. no. 989056085 Limited company (AS) Hvaler Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 15,000
Operating profit NOK −104,000
Equity NOK 1.4m
Incorporated 2005
Share capital NOK 400,000

Signals

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

HAUGER HOLDING AS is registered as a limited company in Hvaler, Østfold with organisation number 989056085. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 400,000, divided into 400 shares. The company's stated purpose is: “Aksjeforvaltning, samt alt som står i naturlig forbindelse med dette, derunder investeringer og deltakelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 15,000 in revenue and NOK −104,000 in operating profit.

Key figures · 2025

Revenue
NOK 15,000
Operating profit
NOK −104,000
Equity
NOK 1.4m
Est. value
NOK 768,000

Financial health · 2025

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

Who owns HAUGER HOLDING AS?

BÅRD BERGEM HAUGER
HAUGER HOLDING AS
NOK 15,000 rev. · NOK −104,000 profit

HAUGER HOLDING AS has 6 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAUGER HOLDING AS

Who owns HAUGER HOLDING AS?

BÅRD BERGEM HAUGER is the largest registered owner, with 37.5%.

What is the revenue of HAUGER HOLDING AS?

HAUGER HOLDING AS had revenue of NOK 15,000 in 2025.

Who is the general manager of HAUGER HOLDING AS?

Jan Hauger is registered as general manager of HAUGER HOLDING AS.

Where is HAUGER HOLDING AS based?

HAUGER HOLDING AS has its business address in Nedgården.

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.