BIZTRAC BETA
Uoppgitt

VB-HOLDING AS

Org. no. 923276645 Limited company (AS) Bergen Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 6,000
Operating profit NOK −3,000
Equity NOK 37,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

VB-HOLDING AS is registered as a limited company in Bergen, Vestland with organisation number 923276645. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Investeringsselskap som har til hensikt å eie flere mindre virksomheter.”. The most recent filed accounts, for the 2025 financial year, show NOK 6,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 6,000
Operating profit
NOK −3,000
Equity
NOK 37,000
Est. value
NOK 23,000

Financial health · 2025

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

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

Who owns VB-HOLDING AS?

VISAHAN KONESWARAN
VB-HOLDING AS
NOK 6,000 rev. · NOK −3,000 profit

VB-HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VB-HOLDING AS own?

VB-HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VB-HOLDING AS

Who owns VB-HOLDING AS?

VISAHAN KONESWARAN is the largest registered owner, with 100.0%.

What is the revenue of VB-HOLDING AS?

VB-HOLDING AS had revenue of NOK 6,000 in 2025.

Who is the general manager of VB-HOLDING AS?

Visahan Koneswaran is registered as general manager of VB-HOLDING AS.

Where is VB-HOLDING AS based?

VB-HOLDING AS has its business address in Fyllingsdalen.

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.