BIZTRAC BETA
Plumbing installation

AQUATEK AS

Org. no. 931080504 Limited company (AS) Stord Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 35,000
Operating profit NOK −124,000
Equity NOK 429,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−124k kr).

AQUATEK AS is registered as a limited company in Stord, Vestland with organisation number 931080504. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rør innen industri og marine. Utvikle produkter av plastsveis, rør og plastplater i PE for industri, marine, aquakultur, offshore og anleggsbransjen. Selskapets formål er også å kunne gi gaver til humanitære og veldedige organisasjoner.”. The most recent filed accounts, for the 2025 financial year, show NOK 35,000 in revenue and NOK −124,000 in operating profit.

Key figures · 2025

Revenue
NOK 35,000
Operating profit
NOK −124,000
Equity
NOK 429,000
Est. value
NOK 197,000

Financial health · 2025

Liquidity
3.75
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
19.0%
Good
Equity as a share of total capital

Who owns AQUATEK AS?

ENERGI & RØRTEKNIKK AS
AQUATEK AS
NOK 35,000 rev. · NOK −124,000 profit

AQUATEK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about AQUATEK AS

Who owns AQUATEK AS?

ENERGI & RØRTEKNIKK AS is the largest registered owner, with 50.0%.

What is the revenue of AQUATEK AS?

AQUATEK AS had revenue of NOK 35,000 in 2025.

Who is the general manager of AQUATEK AS?

Amos Peter Scholz is registered as general manager of AQUATEK AS.

Where is AQUATEK AS based?

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

Report a problem

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