BIZTRAC BETA
Uoppgitt

VESTGLAD HOLDING AS

Org. no. 834342332 Limited company (AS) Nord-Aurdal Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK −13,000
Equity NOK 32,000
Incorporated 2024
Share capital NOK 50,000

Signals

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

VESTGLAD HOLDING AS is registered as a limited company in Nord-Aurdal, Innlandet with organisation number 834342332. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2024. Registered share capital is NOK 50,000, divided into 50000 shares. The company's stated purpose is: “Eie aksjer og investere i virksomheter av enhver art, samt det som står naturlig i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK −13,000 in operating profit.

Key figures · 2025

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

Financial health · 2025

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

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

Who owns VESTGLAD HOLDING AS?

VEGAR GLADHEIM VESTERÅS
VESTGLAD HOLDING AS
NOK 0 rev. · NOK −13,000 profit

VESTGLAD HOLDING AS has 1 registered shareholder:

All shareholders and roles →

Which companies does VESTGLAD HOLDING AS own?

VESTGLAD HOLDING AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VESTGLAD HOLDING AS

Who owns VESTGLAD HOLDING AS?

VEGAR GLADHEIM VESTERÅS is the largest registered owner, with 100.0%.

What is the revenue of VESTGLAD HOLDING AS?

VESTGLAD HOLDING AS had revenue of NOK 0 in 2025.

Where is VESTGLAD HOLDING AS based?

VESTGLAD HOLDING AS has its business address in Fagernes.

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.