BIZTRAC BETA
Other captive investment companies

VIVA HOLDING AS

Org. no. 989229990 Limited company (AS) Trondheim Incorporated 2005 Active
Ownership graph ↗
Operating profit NOK −21,000
Equity NOK −68,000
Incorporated 2005
Share capital NOK 55,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−68k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−21k kr).

VIVA HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 989229990. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2005. Registered share capital is NOK 55,000, divided into 55 shares. The company's stated purpose is: “Kjøp og salg av aksjer, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet. Firmaet skal også utføre konsulenttjenster for eksterne oppdragsgivere.”.

Key figures · 2024

Operating profit
NOK −21,000
Equity
NOK −68,000

Financial health · 2024

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

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

Who owns VIVA HOLDING AS?

VIGGO RANGNES
VIVA HOLDING AS
· NOK −21,000 profit

VIVA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIVA HOLDING AS own?

VIVA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIVA HOLDING AS

Who owns VIVA HOLDING AS?

VIGGO RANGNES is the largest registered owner, with 100.0%.

Who is the general manager of VIVA HOLDING AS?

Viggo Rangnes is registered as general manager of VIVA HOLDING AS.

Where is VIVA HOLDING AS based?

VIVA HOLDING AS has its business address in Trondheim.

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.