BIZTRAC BETA
Uoppgitt

WRH HOLDING AS

Org. no. 934078276 Limited company (AS) Molde Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −22,000
Equity NOK 3,000
Incorporated 2024
Share capital NOK 30,000

Signals

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

WRH HOLDING AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 934078276. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investere i, eie, forvalte og selge andeler i andre selskaper, samt å utøve aktiviteter som er komplementære til disse, inkludert, men ikke begrenset til, finansiell rådgivning og forvaltning.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −22,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −22,000
Equity
NOK 3,000
Est. value
NOK 3,000

Financial health · 2025

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

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

Who owns WRH HOLDING AS?

WILLY ROGER HUSBY
WRH HOLDING AS
NOK 0 rev. · NOK −22,000 profit

WRH HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does WRH HOLDING AS own?

WRH HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about WRH HOLDING AS

Who owns WRH HOLDING AS?

WILLY ROGER HUSBY is the largest registered owner, with 100.0%.

What is the revenue of WRH HOLDING AS?

WRH HOLDING AS had revenue of NOK 0 in 2025.

Where is WRH HOLDING AS based?

WRH HOLDING AS has its business address in Raudsand.

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.