BIZTRAC BETA
Water collection, treatment and supply

BROKKE VATN OG AVLAUPSVERK AS

Org. no. 984099118 Limited company (AS) Valle Incorporated 2001 Active
Ownership graph ↗
Revenue 2025 NOK 4.7m
Operating profit NOK 1.5m
Equity NOK 7.4m
Incorporated 2001
Share capital NOK 131,000

BROKKE VATN OG AVLAUPSVERK AS is registered as a limited company in Valle, Agder with organisation number 984099118. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2001. Registered share capital is NOK 131,000, divided into 1310 shares. The company's stated purpose is: “Drift av vatn- og kloakkverk, samt hva hermed står i forbindelse, herunder å delta i andre selskap.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.7m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 4.7m
Operating profit
NOK 1.5m
Equity
NOK 7.4m
Est. value
NOK 8.1m

Financial health · 2025

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

Who owns BROKKE VATN OG AVLAUPSVERK AS?

SG NOMELAND AS
BROKKE VATN OG AVLAUPSVERK AS
NOK 4.7m rev. · NOK 1.5m profit

BROKKE VATN OG AVLAUPSVERK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about BROKKE VATN OG AVLAUPSVERK AS

Who owns BROKKE VATN OG AVLAUPSVERK AS?

SG NOMELAND AS is the largest registered owner, with 50.9%.

What is the revenue of BROKKE VATN OG AVLAUPSVERK AS?

BROKKE VATN OG AVLAUPSVERK AS had revenue of NOK 4.7m in 2025.

Who is the general manager of BROKKE VATN OG AVLAUPSVERK AS?

Steinar Nomeland is registered as general manager of BROKKE VATN OG AVLAUPSVERK AS.

Where is BROKKE VATN OG AVLAUPSVERK AS based?

BROKKE VATN OG AVLAUPSVERK AS has its business address in Rysstad.

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.