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

BREIVATN VANN OG RENSEANLEGG SA

Org. no. 919410787 Co-operation (SA) Vinje Incorporated 2005 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK 1,000
Incorporated 2005

BREIVATN VANN OG RENSEANLEGG SA is registered as a co-operation in Vinje, Telemark with organisation number 919410787. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2005. The company's stated purpose is: “Eie, bygge og drifte vann og avløpsanlegg, derunder renseanlegg for andelseiernes eiendommer, hytteeiendommer ved Breivatten i Vinje kommune.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 1,000
Est. value
NOK 1,000

Financial health · 2025

Liquidity
–
Not available
Current assets ÷ current liabilities
Profitability
0.0%
Not satisfactory
Return on total assets
Solidity
100.0%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns BREIVATN VANN OG RENSEANLEGG SA?

No shareholders are registered for BREIVATN VANN OG RENSEANLEGG SA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about BREIVATN VANN OG RENSEANLEGG SA

What is the revenue of BREIVATN VANN OG RENSEANLEGG SA?

BREIVATN VANN OG RENSEANLEGG SA had revenue of NOK 0 in 2025.

Who is the general manager of BREIVATN VANN OG RENSEANLEGG SA?

Signe Jorunn Skamfer Johnsen is registered as general manager of BREIVATN VANN OG RENSEANLEGG SA.

Where is BREIVATN VANN OG RENSEANLEGG SA based?

BREIVATN VANN OG RENSEANLEGG SA has its business address in Vinje.

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.