BIZTRAC BETA
Rental and operating of own or leased real estate

WIUM HOLDING AS

Org. no. 926725432 Limited company (AS) Holmestrand Incorporated 2021 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK 15,000
Incorporated 2021
Share capital NOK 30,000

Signals

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

WIUM HOLDING AS is registered as a limited company in Holmestrand, Vestfold with organisation number 926725432. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Kjøp, salg, utvikling og drift av eiendom, samt annen virksomhet som naturlig hører sammen med dette, herunder å delta i andre selskap, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”.

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK 15,000
Est. value
NOK 14,000

Financial health · 2025

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns WIUM HOLDING AS?

HENNING WIUM
WIUM HOLDING AS
· NOK −3,000 profit

WIUM HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WIUM HOLDING AS own?

WIUM HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about WIUM HOLDING AS

Who owns WIUM HOLDING AS?

HENNING WIUM is the largest registered owner, with 100.0%.

Who is the general manager of WIUM HOLDING AS?

Henning Wium is registered as general manager of WIUM HOLDING AS.

Where is WIUM HOLDING AS based?

WIUM HOLDING AS has its business address in Holmestrand.

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.