BIZTRAC BETA
Uoppgitt

VINSVOLL INVEST AS

Org. no. 898269582 Limited company (AS) Øvre Eiker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −30,000
Equity NOK 2.1m
Incorporated 2012
Share capital NOK 30,000

Signals

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

VINSVOLL INVEST AS is registered as a limited company in Øvre Eiker, Buskerud with organisation number 898269582. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Investering i aksjer og andeler samt i fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −30,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −30,000
Equity
NOK 2.1m
Est. value
NOK 1.4m

Financial health · 2025

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

Who owns VINSVOLL INVEST AS?

HANS OLAV SCHINNES
VINSVOLL INVEST AS
NOK 0 rev. · NOK −30,000 profit

VINSVOLL INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VINSVOLL INVEST AS own?

VINSVOLL INVEST AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about VINSVOLL INVEST AS

Who owns VINSVOLL INVEST AS?

HANS OLAV SCHINNES is the largest registered owner, with 100.0%.

What is the revenue of VINSVOLL INVEST AS?

VINSVOLL INVEST AS had revenue of NOK 0 in 2024.

Who is the general manager of VINSVOLL INVEST AS?

Hans Olav Schinnes is registered as general manager of VINSVOLL INVEST AS.

Where is VINSVOLL INVEST AS based?

VINSVOLL INVEST AS has its business address in Hokksund.

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.