BIZTRAC BETA
Uoppgitt

ULVATN HOLDING AS

Org. no. 927991330 Limited company (AS) Alver Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −16,000
Equity NOK 5.2m
Incorporated 2021
Share capital NOK 30,000

Signals

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

ULVATN HOLDING AS is registered as a limited company in Alver, Vestland with organisation number 927991330. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kjøp, salg og forvaltning av aksjer, andeler, verdipapirer og eiendommer, samt alt som naturlig har sammenheng med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −16,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −16,000
Equity
NOK 5.2m
Est. value
NOK 6.0m

Financial health · 2024

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

Who owns ULVATN HOLDING AS?

ROAR ULVATN
ULVATN HOLDING AS
NOK 0 rev. · NOK −16,000 profit

ULVATN HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ULVATN HOLDING AS own?

ULVATN HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ULVATN HOLDING AS

Who owns ULVATN HOLDING AS?

ROAR ULVATN is the largest registered owner, with 100.0%.

What is the revenue of ULVATN HOLDING AS?

ULVATN HOLDING AS had revenue of NOK 0 in 2024.

Who is the general manager of ULVATN HOLDING AS?

Roar Ulvatn is registered as general manager of ULVATN HOLDING AS.

Where is ULVATN HOLDING AS based?

ULVATN HOLDING AS has its business address in Manger.

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.