BIZTRAC BETA
Collection of hazardous waste

VEGLO HOLDING AS

Org. no. 989213105 Limited company (AS) Stjørdal Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 42,000
Operating profit NOK −124,000
Equity NOK 9.5m
Incorporated 2005
Share capital NOK 1.1m

Signals

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

VEGLO HOLDING AS is registered as a limited company in Stjørdal, Trøndelag with organisation number 989213105. The business is classified under collection of hazardous waste (NACE 38.120). The company was incorporated in 2005. Registered share capital is NOK 1.1m, divided into 1000 shares. The company's stated purpose is: “Forvaltning av kapital, kjøp og salg, videreutvikling og utleie av fast eiendom, og tilhørende virksomhet som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 42,000 in revenue and NOK −124,000 in operating profit.

Key figures · 2025

Revenue
NOK 42,000
Operating profit
NOK −124,000
Equity
NOK 9.5m
Est. value
NOK 6.3m

Financial health · 2025

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

Who owns VEGLO HOLDING AS?

ARVE ANGELL VEGLO
VEGLO HOLDING AS
NOK 42,000 rev. · NOK −124,000 profit

VEGLO HOLDING AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VEGLO HOLDING AS own?

VEGLO HOLDING AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about VEGLO HOLDING AS

Who owns VEGLO HOLDING AS?

ARVE ANGELL VEGLO is the largest registered owner, with 75.0%.

What is the revenue of VEGLO HOLDING AS?

VEGLO HOLDING AS had revenue of NOK 42,000 in 2025.

Where is VEGLO HOLDING AS based?

VEGLO HOLDING AS has its business address in Hell.

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.