BIZTRAC BETA
Other real estate activities on a fee or contract basis

VASTO AS

Org. no. 925140090 Limited company (AS) Ålesund Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 2.6m
Operating profit NOK 1.5m
Equity NOK 12.8m
Incorporated 2020
Share capital NOK 3.2m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

VASTO AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 925140090. The business is classified under other real estate activities on a fee or contract basis (NACE 68.320). The company was incorporated in 2020. Registered share capital is NOK 3.2m, divided into 50 shares. The company's stated purpose is: “Investere i og forvalte eierposter i andre selskaper og i fast eiendom og hva som der følger med.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.6m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 2.6m
Operating profit
NOK 1.5m
Equity
NOK 12.8m
Est. value
NOK 10.9m

Financial health · 2025

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

Who owns VASTO AS?

HØGBØEN AS
VASTO AS
NOK 2.6m rev. · NOK 1.5m profit

VASTO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does VASTO AS own?

VASTO AS holds stakes in 4 companies:

See the full ownership structure →

Frequently asked questions about VASTO AS

Who owns VASTO AS?

HØGBØEN AS is the largest registered owner, with 50.0%.

What is the revenue of VASTO AS?

VASTO AS had revenue of NOK 2.6m in 2025.

Who is the general manager of VASTO AS?

Joakim Valde is registered as general manager of VASTO AS.

Where is VASTO AS based?

VASTO AS has its business address in Skodje.

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.