BIZTRAC BETA
Rental and operating of own or leased real estate

GUSTAVSEN HOLDING AS

Org. no. 931497839 Limited company (AS) Fredrikstad Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −22,000
Equity NOK 67.7m
Incorporated 2023
Share capital NOK 8.1m

Signals

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

GUSTAVSEN HOLDING AS is registered as a limited company in Fredrikstad, Østfold with organisation number 931497839. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2023. Registered share capital is NOK 8.1m, divided into 5433 shares. The company's stated purpose is: “Eie og forvalte andeler i andre foretak samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 67.7m
Est. value
NOK 54.3m

Financial health · 2024

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

Who owns GUSTAVSEN HOLDING AS?

BW GUSTAVSEN AS
GUSTAVSEN HOLDING AS
NOK 0 rev. · NOK −22,000 profit

GUSTAVSEN HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does GUSTAVSEN HOLDING AS own?

GUSTAVSEN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about GUSTAVSEN HOLDING AS

Who owns GUSTAVSEN HOLDING AS?

BW GUSTAVSEN AS is the largest registered owner, with 40.0%.

What is the revenue of GUSTAVSEN HOLDING AS?

GUSTAVSEN HOLDING AS had revenue of NOK 0 in 2024.

Where is GUSTAVSEN HOLDING AS based?

GUSTAVSEN HOLDING AS has its business address in Fredrikstad.

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.