BIZTRAC BETA
Business and other management consultancy activities

AQUA III AS

Org. no. 929535499 Limited company (AS) Nærøysund Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −2,000
Equity NOK 13,000
Incorporated 2022
Share capital NOK 30,000

Signals

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

AQUA III AS is registered as a limited company in Nærøysund, Trøndelag with organisation number 929535499. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Generell investeringsrådgivning.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −2,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −2,000
Equity
NOK 13,000
Est. value
NOK 22,000

Financial health · 2024

Liquidity
Not available
Current assets ÷ current liabilities
Profitability
Not available
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 III AS?

FREYJA FLEET MANAGEMENT AS
AQUA III AS
NOK 0 rev. · NOK −2,000 profit

AQUA III AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AQUA III AS er morselskap for 37 datterselskaper:

Frequently asked questions about AQUA III AS

Who owns AQUA III AS?

FREYJA FLEET MANAGEMENT AS is the largest registered owner, with 100.0%.

What is the revenue of AQUA III AS?

AQUA III AS had revenue of NOK 0 in 2024.

Where is AQUA III AS based?

AQUA III AS has its business address in Kolvereid.

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.