BIZTRAC BETA
Work training and permanently adapted work

ÅLESUND VEKST AS

Org. no. 959347425 Limited company (AS) Ålesund Incorporated 1990 Active
Ownership graph ↗
Revenue 2024 NOK 18.2m
Operating profit NOK −986,000
Equity NOK 7.9m
Incorporated 1990
Employees 54
Share capital NOK 250,000

Signals

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

ÅLESUND VEKST AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 959347425. The business is classified under work training and permanently adapted work (NACE 88.993). The company was incorporated in 1990 and has 54 registered employees. Registered share capital is NOK 250,000, divided into 5 shares. The company's stated purpose is: “Produksjon, produktutvikling, fabrikasjon, salgsvirksomhet og annen næringsvirksomhet for på den måten skape grunnlag for sysselsetting for mennesker med funksjonshemming. ”. The most recent filed accounts, for the 2024 financial year, show NOK 18.2m in revenue and NOK −986,000 in operating profit.

Key figures · 2024

Revenue
NOK 18.2m
Operating profit
NOK −986,000
Equity
NOK 7.9m
Est. value
NOK 18.9m

Financial health · 2024

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

Who owns ÅLESUND VEKST AS?

No shareholders are registered for ÅLESUND VEKST AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ÅLESUND VEKST AS

What is the revenue of ÅLESUND VEKST AS?

ÅLESUND VEKST AS had revenue of NOK 18.2m in 2024.

Who is the general manager of ÅLESUND VEKST AS?

Marius Finsæther Øksenvåg is registered as general manager of ÅLESUND VEKST AS.

Where is ÅLESUND VEKST AS based?

ÅLESUND VEKST AS has its business address in Ålesund.

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.