biztrac. BETA
COMPANY REGISTER PROFILE
916961111 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other captive investment companies

V-ONE AS

Org. no. 916961111 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK −70
Operating profit NOK −3,000
Equity NOK 20,000
Incorporated 2016
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

V-ONE AS is registered as a limited company in Oslo, Oslo with organisation number 916961111. The business is classified under other captive investment companies (NACE 64.323). The company was incorporated in 2016. Registered share capital is NOK 50,000, divided into 1000 shares. The company's stated purpose is: “Holdingselskap for en finansiell investering i et annet selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK −70 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK −70
Operating profit
NOK −3,000
▼ −836 %
Equity
NOK 20,000
▼ −13 %
Est. value
NOK 18,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
-0.9%
Not satisfactory
Return on total assets
Solidity
5.8%
Weak
Equity as a share of total capital

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

Who owns V-ONE AS?

V-ONE AS has 3 registered shareholders:

All shareholders and roles →

Which companies does V-ONE AS own?

V-ONE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about V-ONE AS

Who owns V-ONE AS?

KOGRA AS is the largest registered owner, with 33.4%.

What is the revenue of V-ONE AS?

V-ONE AS had revenue of NOK −70 in 2025.

Who is the general manager of V-ONE AS?

Simen Hoem Langsholt is registered as general manager of V-ONE AS.

Where is V-ONE AS based?

V-ONE 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.