biztrac. BETA
COMPANY REGISTER PROFILE
834319152 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Other investment companies, except captive companies

ENVISION SPV I AS

Org. no. 834319152 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −3,000
Equity NOK −9,000
Incorporated 2024
Share capital NOK 1.7m

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−9k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).
  • Nylig endring 2026-08-26 Aksjekapital registrert 2026-08-26.

ENVISION SPV I AS is registered as a limited company in Oslo, Oslo with organisation number 834319152. The business is classified under other investment companies, except captive companies (NACE 64.312). The company was incorporated in 2024. Registered share capital is NOK 1.7m, divided into 83315927 shares. The company's stated purpose is: “Investere i aksjer og andre finansielle instrumenter, og alt som er forbundet med dette.”.

Former names: VIOS 271 AS, ENVISION GP II AS

Key figures · 2025

Operating profit
NOK −3,000
Equity
NOK −9,000
▼ −148 %

Financial health · 2025

Liquidity
0.39
Not satisfactory
Current assets ÷ current liabilities
Profitability
-7.3%
Not satisfactory
Return on total assets
Solidity
-26.9%
Weak
Equity as a share of total capital

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

Who owns ENVISION SPV I AS?

ENVISION SPV I AS
· NOK −3,000 profit

ENVISION SPV I AS has 1 registered shareholder:

All shareholders and roles →

Which companies does ENVISION SPV I AS own?

ENVISION SPV I AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about ENVISION SPV I AS

Who owns ENVISION SPV I AS?

C.P. FINNE AS is the largest registered owner, with 100.0%.

Where is ENVISION SPV I AS based?

ENVISION SPV I 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.