BIZTRAC BETA
Non-specialised wholesale trade

AQUA UNIQUE NORGE AS

Org. no. 975820300 Limited company (AS) Lier Incorporated 1995 Active
Ownership graph ↗
Revenue 2024 NOK 18.4m
Operating profit NOK 100,000
Equity NOK 2.8m
Incorporated 1995
Share capital NOK 100,000

AQUA UNIQUE NORGE AS is registered as a limited company in Lier, Buskerud with organisation number 975820300. The business is classified under non-specialised wholesale trade (NACE 46.900). The company was incorporated in 1995. Registered share capital is NOK 100,000, divided into 50 shares. The company's stated purpose is: “Handel, import og eksport innenfor vannbehandling og shippingindustrien, og dertil tilhørende konsulentvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.4m in revenue and NOK 100,000 in operating profit.

Key figures · 2024

Revenue
NOK 18.4m
Operating profit
NOK 100,000
Equity
NOK 2.8m
Est. value
NOK 1.7m

Financial health · 2024

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

Who owns AQUA UNIQUE NORGE AS?

GAZELLE DEVELOPMENT AS
AQUA UNIQUE NORGE AS
NOK 18.4m rev. · NOK 100,000 profit

AQUA UNIQUE NORGE AS has 1 registered shareholder:

All shareholders and roles →

Group structure

AQUA UNIQUE NORGE AS er morselskap for 1 datterselskap:

Frequently asked questions about AQUA UNIQUE NORGE AS

Who owns AQUA UNIQUE NORGE AS?

GAZELLE DEVELOPMENT AS is the largest registered owner, with 100.0%.

What is the revenue of AQUA UNIQUE NORGE AS?

AQUA UNIQUE NORGE AS had revenue of NOK 18.4m in 2024.

Who is the general manager of AQUA UNIQUE NORGE AS?

Per Henriksen is registered as general manager of AQUA UNIQUE NORGE AS.

Where is AQUA UNIQUE NORGE AS based?

AQUA UNIQUE NORGE AS has its business address in Lierskogen.

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.