BIZTRAC BETA
Buying and selling of own real estate

ÅRØ VEKST AS

Org. no. 834403552 Limited company (AS) Molde Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −27,000
Equity NOK 6,000
Incorporated 2024
Share capital NOK 100,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−27k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

ÅRØ VEKST AS is registered as a limited company in Molde, Møre og Romsdal with organisation number 834403552. The business is classified under buying and selling of own real estate (NACE 68.110). The company was incorporated in 2024. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Å eie og leie ut næringsbygg og eiendom, og annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender og annet som naturlig faller sammen med dette.”.

Key figures · 2024

Operating profit
NOK −27,000
Equity
NOK 6,000
Est. value
NOK 6,000

Financial health · 2024

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

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

Who owns ÅRØ VEKST AS?

H.O. SØBSTAD AS
ÅRØ VEKST AS
· NOK −27,000 profit

ÅRØ VEKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅRØ VEKST AS

Who owns ÅRØ VEKST AS?

H.O. SØBSTAD AS is the largest registered owner, with 100.0%.

Who is the general manager of ÅRØ VEKST AS?

Hans Olav Søbstad is registered as general manager of ÅRØ VEKST AS.

Where is ÅRØ VEKST AS based?

ÅRØ VEKST AS has its business address in Molde.

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.