BIZTRAC BETA
Uoppgitt

VI-LA HOLDING AS

Org. no. 836662962 Limited company (AS) Orkland Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −26,000
Equity NOK 2.1m
Incorporated 2025
Share capital NOK 178,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−26k kr).
  • Nystiftet selskap Selskapet ble stiftet 2025-09-12.

VI-LA HOLDING AS is registered as a limited company in Orkland, Trøndelag with organisation number 836662962. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 178,000, divided into 200 shares. The company's stated purpose is: “Eie aksjer i aksjeselskap og tilsvarende investeringer.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −26,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −26,000
Equity
NOK 2.1m
Est. value
NOK 2.4m

Financial health · 2025

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

Who owns VI-LA HOLDING AS?

VIDAR LANDRØ
VI-LA HOLDING AS
NOK 0 rev. · NOK −26,000 profit

VI-LA HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VI-LA HOLDING AS own?

VI-LA HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VI-LA HOLDING AS

Who owns VI-LA HOLDING AS?

VIDAR LANDRØ is the largest registered owner, with 100.0%.

What is the revenue of VI-LA HOLDING AS?

VI-LA HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of VI-LA HOLDING AS?

Vidar Landrø is registered as general manager of VI-LA HOLDING AS.

Where is VI-LA HOLDING AS based?

VI-LA HOLDING AS has its business address in Gjølme.

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.