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

INDRE AVERØY VANNVERK SA

Org. no. 870186762 Co-operation (SA) Averøy Incorporated 1970 Active
Ownership graph ↗
Revenue 2025 NOK 3.4m
Operating profit NOK 370,000
Equity NOK 4.8m
Incorporated 1970

INDRE AVERØY VANNVERK SA is registered as a co-operation in Averøy, Møre og Romsdal with organisation number 870186762. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 1970. The company's stated purpose is: “Skaffe vann til husbruk, jordbruk og industri mv, innen de områder som naturlig hører inn under lagets vannforsyningsområde. Andelslaget drives til selvkost.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.4m in revenue and NOK 370,000 in operating profit.

Former names: INDRE AVERØY VANNVERK A/L, INDRE AVERØY VANNVERK BA

Key figures · 2025

Revenue
NOK 3.4m
▼ −0 %
Operating profit
NOK 370,000
▼ −25 %
Equity
NOK 4.8m
▲ +1 %
Est. value
NOK 4.1m

Financial health · 2025

Liquidity
2.41
Very good
Current assets ÷ current liabilities
Profitability
3.4%
Weak
Return on total assets
Solidity
44.4%
Very good
Equity as a share of total capital

Who owns INDRE AVERØY VANNVERK SA?

No shareholders are registered for INDRE AVERØY VANNVERK SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about INDRE AVERØY VANNVERK SA

What is the revenue of INDRE AVERØY VANNVERK SA?

INDRE AVERØY VANNVERK SA had revenue of NOK 3.4m in 2025.

Who is the general manager of INDRE AVERØY VANNVERK SA?

Arnstein Punde Dragsten is registered as general manager of INDRE AVERØY VANNVERK SA.

Where is INDRE AVERØY VANNVERK SA based?

INDRE AVERØY VANNVERK 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.