BIZTRAC BETA
Other building and industrial cleaning activities

ALGENMAX AS

Org. no. 933033317 Limited company (AS) Tysvær Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 7.1m
Operating profit NOK −504,000
Equity NOK 363,000
Incorporated 2024
Employees 9
Share capital NOK 1.0m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−504k kr).

ALGENMAX AS is registered as a limited company in Tysvær, Rogaland with organisation number 933033317. The business is classified under other building and industrial cleaning activities (NACE 81.220). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 1.0m, divided into 1030000 shares. The company's stated purpose is: “Drive med utvendig rengjøring av bygninger og industriell rengjøring, samt andre tjenester og virksomheter som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 7.1m in revenue and NOK −504,000 in operating profit.

Key figures · 2025

Revenue
NOK 7.1m
Operating profit
NOK −504,000
Equity
NOK 363,000
Est. value
NOK 4.7m

Financial health · 2025

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

Who owns ALGENMAX AS?

SØDER AS
ALGENMAX AS
NOK 7.1m rev. · NOK −504,000 profit

ALGENMAX AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about ALGENMAX AS

Who owns ALGENMAX AS?

SØDER AS is the largest registered owner, with 60.0%.

What is the revenue of ALGENMAX AS?

ALGENMAX AS had revenue of NOK 7.1m in 2025.

Who is the general manager of ALGENMAX AS?

Alexander Toft Søderlund is registered as general manager of ALGENMAX AS.

Where is ALGENMAX AS based?

ALGENMAX AS has its business address in Førresfjorden.

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.