biztrac. BETA
COMPANY REGISTER PROFILE
931510827 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
In liquidation UPDATED 03.10.2026
⚠VIVA SUSTAINABLE AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Wholesale of other intermediate products

VIVA SUSTAINABLE AS

Org. no. 931510827 Limited company (AS) Oslo Incorporated 2023 In liquidation
Revenue 2025 NOK 0
Operating profit NOK −8,000
Equity NOK 50,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

VIVA SUSTAINABLE AS is registered as a limited company in Oslo, Oslo with organisation number 931510827. The business is classified under wholesale of other intermediate products (NACE 46.860). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Salg av emballasje.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
▼ −100 %
Operating profit
NOK −8,000
▼ −205 %
Equity
NOK 50,000
▼ −12 %

Financial health · 2025

Liquidity
-7.10
Not satisfactory
Current assets ÷ current liabilities
Profitability
-13.2%
Not satisfactory
Return on total assets
Solidity
114.1%
Weak
Equity as a share of total capital

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

Who owns VIVA SUSTAINABLE AS?

VIVA SUSTAINABLE AS
NOK 0 rev. · NOK −8,000 profit

VIVA SUSTAINABLE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about VIVA SUSTAINABLE AS

Who owns VIVA SUSTAINABLE AS?

Øystein Bergan Himle is the largest registered owner, with 50.0%.

What is the revenue of VIVA SUSTAINABLE AS?

VIVA SUSTAINABLE AS had revenue of NOK 0 in 2025.

Where is VIVA SUSTAINABLE AS based?

VIVA SUSTAINABLE AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.