BIZTRAC BETA
Wholesale of pharmaceutical and medical goods

VESK INVEST AS

Org. no. 930801232 Limited company (AS) Sandnes Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −18,000
Equity NOK 102,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

VESK INVEST AS is registered as a limited company in Sandnes, Rogaland with organisation number 930801232. The business is classified under wholesale of pharmaceutical and medical goods (NACE 46.460). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −18,000 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK −18,000
Equity
NOK 102,000
Est. value
NOK 763,000

Financial health · 2025

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

Who owns VESK INVEST AS?

VEGARD SKÅRLAND
VESK INVEST AS
NOK 0 rev. · NOK −18,000 profit

VESK INVEST AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VESK INVEST AS own?

VESK INVEST AS holds a stake in 1 company:

See the full ownership structure →

Group structure

VESK INVEST AS er morselskap for 1 datterselskap:

Frequently asked questions about VESK INVEST AS

Who owns VESK INVEST AS?

VEGARD SKÅRLAND is the largest registered owner, with 100.0%.

What is the revenue of VESK INVEST AS?

VESK INVEST AS had revenue of NOK 0 in 2025.

Where is VESK INVEST AS based?

VESK INVEST AS has its business address in Sandnes.

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.