BIZTRAC BETA
Site preparation

VEGUSDAL ANLEGG AS

Org. no. 980400182 Limited company (AS) Arendal Incorporated 1998 Active
Ownership graph ↗
Revenue 2024 NOK 2.9m
Operating profit NOK −707,000
Equity NOK 2.8m
Incorporated 1998
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−707k kr).

VEGUSDAL ANLEGG AS is registered as a limited company in Arendal, Agder with organisation number 980400182. The business is classified under site preparation (NACE 43.120). The company was incorporated in 1998. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Diverse anleggsvirksomhet innen bygg og eiendom, diverse varetransport av gods på veg samt alt hva hermed står i forbindelse herunder deltagelse i andre selskaper med.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.9m in revenue and NOK −707,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.9m
Operating profit
NOK −707,000
Equity
NOK 2.8m
Est. value
NOK 2.2m

Financial health · 2024

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

Who owns VEGUSDAL ANLEGG AS?

JONN HELGE FLATELAND
VEGUSDAL ANLEGG AS
NOK 2.9m rev. · NOK −707,000 profit

VEGUSDAL ANLEGG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VEGUSDAL ANLEGG AS

Who owns VEGUSDAL ANLEGG AS?

JONN HELGE FLATELAND is the largest registered owner, with 100.0%.

What is the revenue of VEGUSDAL ANLEGG AS?

VEGUSDAL ANLEGG AS had revenue of NOK 2.9m in 2024.

Who is the general manager of VEGUSDAL ANLEGG AS?

Jonn Helge Flateland is registered as general manager of VEGUSDAL ANLEGG AS.

Where is VEGUSDAL ANLEGG AS based?

VEGUSDAL ANLEGG AS has its business address in Kongshavn.

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.