BIZTRAC BETA
Operation of marine fish farms

ALGEVEKST AS

Org. no. 923734317 Limited company (AS) Aure Incorporated 2019 Active
Ownership graph ↗
Revenue 2025 NOK 13,000
Operating profit NOK −8,000
Equity NOK −286,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−286k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−8k kr).

ALGEVEKST AS is registered as a limited company in Aure, Møre og Romsdal with organisation number 923734317. The business is classified under operation of marine fish farms (NACE 03.211). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Dyrking av makroalger og andre nærliggende blødyr, og det som naturlig tilhører under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 13,000 in revenue and NOK −8,000 in operating profit.

Key figures · 2025

Revenue
NOK 13,000
Operating profit
NOK −8,000
Equity
NOK −286,000

Financial health · 2025

Liquidity
0.26
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-285.0%
Weak
Equity as a share of total capital

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

Who owns ALGEVEKST AS?

BJØRN ARILD SØYSETH
ALGEVEKST AS
NOK 13,000 rev. · NOK −8,000 profit

ALGEVEKST AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ALGEVEKST AS

Who owns ALGEVEKST AS?

BJØRN ARILD SØYSETH is the largest registered owner, with 100.0%.

What is the revenue of ALGEVEKST AS?

ALGEVEKST AS had revenue of NOK 13,000 in 2025.

Who is the general manager of ALGEVEKST AS?

Bjørn Arild Søyseth is registered as general manager of ALGEVEKST AS.

Where is ALGEVEKST AS based?

ALGEVEKST AS has its business address in Tustna.

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.