biztrac. BETA
COMPANY REGISTER PROFILE
914827922 ORG. NO. 2025 ACCOUNTS 9 SECTIONS
Active UPDATED 03.10.2026
Collection of non-hazardous waste

AQUAPRO AS

Org. no. 914827922 Limited company (AS) Stord Incorporated 2015 Active
Revenue 2025 NOK 1.7m
Operating profit NOK 616,000
Equity NOK 1.2m
Incorporated 2015
Share capital NOK 4.6m

AQUAPRO AS is registered as a limited company in Stord, Vestland with organisation number 914827922. The business is classified under collection of non-hazardous waste (NACE 38.110). The company was incorporated in 2015. Registered share capital is NOK 4.6m, divided into 4588 shares. The company's stated purpose is: “Drive med renovasjons logistikk og renseteknologi.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.7m in revenue and NOK 616,000 in operating profit.

Former names: IBOX KOMMUNIKASJON AS

Key figures · 2025

Revenue
NOK 1.7m
▲ +319 %
Operating profit
NOK 616,000
▲ +179 %
Equity
NOK 1.2m
▲ +42 %
Est. value
NOK 2.6m

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
10.5%
Good
Return on total assets
Solidity
19.6%
Good
Equity as a share of total capital

Who owns AQUAPRO AS?

AQUAPRO AS
NOK 1.7m rev. · NOK 616,000 profit

AQUAPRO AS has 2 registered shareholders:

All shareholders and roles →

Which companies does AQUAPRO AS own?

AQUAPRO AS holds a stake in 1 company:

See the full ownership structure →

Group structure

AQUAPRO AS er morselskap for 6 datterselskaper:

Frequently asked questions about AQUAPRO AS

Who owns AQUAPRO AS?

RAGN SELLS AS is the largest registered owner, with 84.9%.

What is the revenue of AQUAPRO AS?

AQUAPRO AS had revenue of NOK 1.7m in 2025.

Who is the general manager of AQUAPRO AS?

Ole Arthur Vaage is registered as general manager of AQUAPRO AS.

Where is AQUAPRO AS based?

AQUAPRO AS has its business address in Stord.

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.