biztrac. BETA
COMPANY REGISTER PROFILE
870526202 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Water collection, treatment and supply

HOEL VASSVERK SA

Org. no. 870526202 Co-operation (SA) Averøy Incorporated 1963 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 34,000
Equity NOK 815,000
Incorporated 1963

HOEL VASSVERK SA is registered as a co-operation in Averøy, Møre og Romsdal with organisation number 870526202. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 1963. The company's stated purpose is: “Produsere og levere vann av kvalitet som tilfredstiller næringsmyndighetenes krav, til sine medlemmer til husbruk, jordbruk, industri m.v. innen det område som naturlig tilhører lagets forsyningsområde. Deltagelse i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 34,000 in operating profit.

Former names: HOEL VASSVERK A/L, HOEL VASSVERK AL, HOEL VASSVERK BA

Key figures · 2025

Revenue
NOK 1.2m
▼ −14 %
Operating profit
NOK 34,000
▼ −85 %
Equity
NOK 815,000
▼ −20 %
Est. value
NOK 789,000

Financial health · 2025

Liquidity
3.40
Very good
Current assets ÷ current liabilities
Profitability
0.9%
Not satisfactory
Return on total assets
Solidity
19.3%
Good
Equity as a share of total capital

Who owns HOEL VASSVERK SA?

No shareholders are registered for HOEL VASSVERK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about HOEL VASSVERK SA

What is the revenue of HOEL VASSVERK SA?

HOEL VASSVERK SA had revenue of NOK 1.2m in 2025.

Who is the general manager of HOEL VASSVERK SA?

Roald Gustad is registered as general manager of HOEL VASSVERK SA.

Where is HOEL VASSVERK SA based?

HOEL VASSVERK SA has its business address in Averøy.

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.