BIZTRAC BETA
Wholesale of information and communication equipment

VSINV AS

Org. no. 930800910 Limited company (AS) Bærum Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −104,000
Equity NOK −81,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VSINV AS is registered as a limited company in Bærum, Akershus with organisation number 930800910. The business is classified under wholesale of information and communication equipment (NACE 46.500). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Å investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2024

Operating profit
NOK −104,000
Equity
NOK −81,000

Financial health · 2024

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

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

Who owns VSINV AS?

Viktor Sigurd Wold Eide
VSINV AS
· NOK −104,000 profit

VSINV AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VSINV AS own?

VSINV AS holds stakes in 3 companies:

See the full ownership structure →

Frequently asked questions about VSINV AS

Who owns VSINV AS?

Viktor Sigurd Wold Eide is the largest registered owner, with 100.0%.

Who is the general manager of VSINV AS?

Viktor Sigurd Wold Eide is registered as general manager of VSINV AS.

Where is VSINV AS based?

VSINV AS has its business address in Gjettum.

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.