BIZTRAC BETA
Uoppgitt

GISLE HAUG HOLDING AS

Org. no. 935701546 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −5,000
Equity NOK 277,000
Incorporated 2025
Share capital NOK 60,000

Signals

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

GISLE HAUG HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 935701546. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 60,000, divided into 30000 shares. The company's stated purpose is: “Eie, kjøpe og selge aksjer og andeler i andre selskaper, samt alt som står i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −5,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −5,000
Equity
NOK 277,000
Est. value
NOK 1.3m

Financial health · 2025

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

Who owns GISLE HAUG HOLDING AS?

GISLE CHRISTOFER HAUG
GISLE HAUG HOLDING AS
NOK 0 rev. · NOK −5,000 profit

GISLE HAUG HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does GISLE HAUG HOLDING AS own?

GISLE HAUG HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Group structure

GISLE HAUG HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about GISLE HAUG HOLDING AS

Who owns GISLE HAUG HOLDING AS?

GISLE CHRISTOFER HAUG is the largest registered owner, with 100.0%.

What is the revenue of GISLE HAUG HOLDING AS?

GISLE HAUG HOLDING AS had revenue of NOK 0 in 2025.

Where is GISLE HAUG HOLDING AS based?

GISLE HAUG HOLDING AS has its business address in Oslo.

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.