BIZTRAC BETA
Uoppgitt

VI82 HOLDING AS

Org. no. 930635294 Limited company (AS) Trondheim Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 32,000
Incorporated 2022
Share capital NOK 30,000

VI82 HOLDING AS is registered as a limited company in Trondheim, Trøndelag with organisation number 930635294. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Å foreta investeringer i aksjer og andre verdipapirer samt deltakelse i andre selskaper og virksomheter, investering i samt kjøp, salg og forvaltning av fast eiendom og oppdrag i forbindelse med fysioterapeutvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 32,000
Est. value
NOK 32,000

Financial health · 2024

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

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

Who owns VI82 HOLDING AS?

VEGARD IVERSEN
VI82 HOLDING AS
NOK 0 rev. · NOK 0 profit

VI82 HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VI82 HOLDING AS own?

VI82 HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Group structure

VI82 HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about VI82 HOLDING AS

Who owns VI82 HOLDING AS?

VEGARD IVERSEN is the largest registered owner, with 100.0%.

What is the revenue of VI82 HOLDING AS?

VI82 HOLDING AS had revenue of NOK 0 in 2024.

Where is VI82 HOLDING AS based?

VI82 HOLDING AS has its business address in Trondheim.

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.