BIZTRAC BETA
Construction of residential and non-residential buildings

VIKING HAUGESUND HOLDING AS

Org. no. 916161417 Limited company (AS) Haugesund Incorporated 2015 Active
Ownership graph ↗
Operating profit NOK −9,000
Equity NOK 2.3m
Incorporated 2015
Share capital NOK 390,000

Signals

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

VIKING HAUGESUND HOLDING AS is registered as a limited company in Haugesund, Rogaland with organisation number 916161417. The business is classified under construction of residential and non-residential buildings (NACE 41.000). The company was incorporated in 2015. Registered share capital is NOK 390,000, divided into 100 shares. The company's stated purpose is: “Eie, investere og delta i andre foretak, samt det som naturlig står i forbindelse med dette.”.

Key figures · 2025

Operating profit
NOK −9,000
Equity
NOK 2.3m
Est. value
NOK 2.3m

Financial health · 2024

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

Who owns VIKING HAUGESUND HOLDING AS?

TOMASZ MARIUSZ WITKOWSKI
VIKING HAUGESUND HOLDING AS
· NOK −9,000 profit

VIKING HAUGESUND HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIKING HAUGESUND HOLDING AS own?

VIKING HAUGESUND HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VIKING HAUGESUND HOLDING AS

Who owns VIKING HAUGESUND HOLDING AS?

TOMASZ MARIUSZ WITKOWSKI is the largest registered owner, with 100.0%.

Who is the general manager of VIKING HAUGESUND HOLDING AS?

Tomasz Mariusz Witkowski is registered as general manager of VIKING HAUGESUND HOLDING AS.

Where is VIKING HAUGESUND HOLDING AS based?

VIKING HAUGESUND HOLDING AS has its business address in Haugesund.

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.