biztrac. BETA
COMPANY REGISTER PROFILE
928016552 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
In liquidation UPDATED 03.10.2026
⚠AQUA-360 AS is registered as “In liquidation” with the Brønnøysund Register Centre.
Civil engineering activities

AQUA-360 AS

Org. no. 928016552 Limited company (AS) Oslo Incorporated 2021 In liquidation
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 93,000
Incorporated 2021
Share capital NOK 100,000

Signals

1 flags
  • Under avvikling Selskapet er under frivillig avvikling.

AQUA-360 AS is registered as a limited company in Oslo, Oslo with organisation number 928016552. The business is classified under civil engineering activities (NACE 71.121). The company was incorporated in 2021. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Utvikling av teknologi for aquakultur, ingeniørtjenester, finne produkter og tjenester for å bedre vannkvalitet. Utleie, salg og teknisk utstyr.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Former names: FROGN UTVIKLING AS

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 93,000
▼ −0 %

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

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

Who owns AQUA-360 AS?

AQUA-360 AS
NOK 0 rev. · NOK 0 profit

AQUA-360 AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AQUA-360 AS

Who owns AQUA-360 AS?

L E HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AQUA-360 AS?

AQUA-360 AS had revenue of NOK 0 in 2025.

Where is AQUA-360 AS based?

AQUA-360 AS has its business address in Oslo.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.