BIZTRAC BETA
Computer consultancy and computer facilities management activities

AQUAECO AS

Org. no. 920312977 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 198,000
Operating profit NOK 156,000
Equity NOK −1.8m
Incorporated 2018
Share capital NOK 100,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,8 mill kr).

AQUAECO AS is registered as a limited company in Oslo, Oslo with organisation number 920312977. The business is classified under computer consultancy and computer facilities management activities (NACE 62.200). The company was incorporated in 2018. Registered share capital is NOK 100,000, divided into 10000000 shares. The company's stated purpose is: “Utvikling av forventningsverdi gjennom investering og utvikling av prosjekter relatert til informasjonsteknologi og bærekraft.”. The most recent filed accounts, for the 2024 financial year, show NOK 198,000 in revenue and NOK 156,000 in operating profit.

Key figures · 2024

Revenue
NOK 198,000
Operating profit
NOK 156,000
Equity
NOK −1.8m
Est. value
NOK 745,000

Financial health · 2024

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

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

Who owns AQUAECO AS?

LOME AS
AQUAECO AS
NOK 198,000 rev. · NOK 156,000 profit

AQUAECO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AQUAECO AS

Who owns AQUAECO AS?

LOME AS is the largest registered owner, with 90.0%.

What is the revenue of AQUAECO AS?

AQUAECO AS had revenue of NOK 198,000 in 2024.

Who is the general manager of AQUAECO AS?

Harald Lome is registered as general manager of AQUAECO AS.

Where is AQUAECO AS based?

AQUAECO 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 15.06.2026.

Report a problem

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