BIZTRAC BETA
Accounting and bookkeeping

VEGAR HOLDING AS

Org. no. 989211560 Limited company (AS) Vestvågøy Incorporated 2005 Active
Ownership graph ↗
Revenue 2024 NOK 2.2m
Operating profit NOK 464,000
Equity NOK 48.6m
Incorporated 2005
Share capital NOK 1.0m

VEGAR HOLDING AS is registered as a limited company in Vestvågøy, Nordland with organisation number 989211560. The business is classified under accounting and bookkeeping (NACE 69.202). The company was incorporated in 2005. Registered share capital is NOK 1.0m, divided into 100 shares. The company's stated purpose is: “Deltakelse og investeringer i andre virksomheter. ”. The most recent filed accounts, for the 2024 financial year, show NOK 2.2m in revenue and NOK 464,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.2m
Operating profit
NOK 464,000
Equity
NOK 48.6m
Est. value
NOK 26.5m

Financial health · 2024

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

Who owns VEGAR HOLDING AS?

GRY CHRISTOFFERSEN
VEGAR HOLDING AS
NOK 2.2m rev. · NOK 464,000 profit

VEGAR HOLDING AS has 5 registered shareholders:

All shareholders and roles →

Which companies does VEGAR HOLDING AS own?

VEGAR HOLDING AS holds stakes in 6 companies:

See the full ownership structure →

Group structure

VEGAR HOLDING AS er morselskap for 1 datterselskap:

Frequently asked questions about VEGAR HOLDING AS

Who owns VEGAR HOLDING AS?

GRY CHRISTOFFERSEN is the largest registered owner, with 24.0%.

What is the revenue of VEGAR HOLDING AS?

VEGAR HOLDING AS had revenue of NOK 2.2m in 2024.

Who is the general manager of VEGAR HOLDING AS?

Gry Christoffersen is registered as general manager of VEGAR HOLDING AS.

Where is VEGAR HOLDING AS based?

VEGAR HOLDING AS has its business address in Ballstad.

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.