BIZTRAC BETA
Uoppgitt

VIVERE HOLDING AS

Org. no. 911966034 Limited company (AS) Tønsberg Incorporated 2013 Active
Ownership graph ↗
Revenue 2024 NOK 182,000
Operating profit NOK −595,000
Equity NOK 9.2m
Incorporated 2013
Share capital NOK 30,000

Signals

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

VIVERE HOLDING AS is registered as a limited company in Tønsberg, Vestfold with organisation number 911966034. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Selskapets virksomhet er kjøp og salg av verdipapirer og fast eiendom, rådgivning og deltagelse i andre virksomheter, utleie av arbeidskraft og annen konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 182,000 in revenue and NOK −595,000 in operating profit.

Key figures · 2024

Revenue
NOK 182,000
Operating profit
NOK −595,000
Equity
NOK 9.2m
Est. value
NOK 32.0m

Financial health · 2025

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

Who owns VIVERE HOLDING AS?

MARIANNE AAS
VIVERE HOLDING AS
NOK 182,000 rev. · NOK −595,000 profit

VIVERE HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VIVERE HOLDING AS own?

VIVERE HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VIVERE HOLDING AS

Who owns VIVERE HOLDING AS?

MARIANNE AAS is the largest registered owner, with 100.0%.

What is the revenue of VIVERE HOLDING AS?

VIVERE HOLDING AS had revenue of NOK 182,000 in 2024.

Where is VIVERE HOLDING AS based?

VIVERE HOLDING AS has its business address in Tønsberg.

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.