BIZTRAC BETA
Uoppgitt

ULLEVÅL HOLDING AS

Org. no. 928771385 Limited company (AS) Rauma Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −24,000
Equity NOK 698,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

ULLEVÅL HOLDING AS is registered as a limited company in Rauma, Møre og Romsdal with organisation number 928771385. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Investeringsvirksomhet, samt kjøp og salg av aksjer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −24,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −24,000
Equity
NOK 698,000
Est. value
NOK 1.2m

Financial health · 2025

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

Who owns ULLEVÅL HOLDING AS?

HENRIK WOLD DEUNK
ULLEVÅL HOLDING AS
NOK 0 rev. · NOK −24,000 profit

ULLEVÅL HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULLEVÅL HOLDING AS own?

ULLEVÅL HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about ULLEVÅL HOLDING AS

Who owns ULLEVÅL HOLDING AS?

HENRIK WOLD DEUNK is the largest registered owner, with 100.0%.

What is the revenue of ULLEVÅL HOLDING AS?

ULLEVÅL HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of ULLEVÅL HOLDING AS?

Henrik Wold Deunk is registered as general manager of ULLEVÅL HOLDING AS.

Where is ULLEVÅL HOLDING AS based?

ULLEVÅL HOLDING AS has its business address in Åndalsnes.

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.