BIZTRAC BETA
Uoppgitt

VESTNES-HOLDING AS

Org. no. 933380009 Limited company (AS) Vestnes Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −10,000
Equity NOK 359,000
Incorporated 2024
Share capital NOK 65,000

Signals

2 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−10k kr).
  • Nylig endring 2026-04-15 Aksjekapital registrert 2026-04-15.

VESTNES-HOLDING AS is registered as a limited company in Vestnes, Møre og Romsdal with organisation number 933380009. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 65,000, divided into 15 shares. The company's stated purpose is: “Eie aksjer og andeler.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −10,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −10,000
Equity
NOK 359,000
Est. value
NOK 422,000

Financial health · 2025

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

Who owns VESTNES-HOLDING AS?

TORE VIK
VESTNES-HOLDING AS
NOK 0 rev. · NOK −10,000 profit

VESTNES-HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VESTNES-HOLDING AS own?

VESTNES-HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VESTNES-HOLDING AS

Who owns VESTNES-HOLDING AS?

TORE VIK is the largest registered owner, with 50.0%.

What is the revenue of VESTNES-HOLDING AS?

VESTNES-HOLDING AS had revenue of NOK 0 in 2025.

Who is the general manager of VESTNES-HOLDING AS?

Terje Vestnes is registered as general manager of VESTNES-HOLDING AS.

Where is VESTNES-HOLDING AS based?

VESTNES-HOLDING AS has its business address in Vestnes.

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.