BIZTRAC BETA
Water collection, treatment and supply

SYNSTEVASSÅSEN VANN OG AVLØP AS

Org. no. 921218559 Limited company (AS) Nesbyen Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 271,000
Operating profit NOK 96,000
Equity NOK 30,000
Incorporated 2018
Share capital NOK 30,000

SYNSTEVASSÅSEN VANN OG AVLØP AS is registered as a limited company in Nesbyen, Buskerud with organisation number 921218559. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Utbygging av og drift av vann- og avløpsanlegg i Synstevassåsen samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 271,000 in revenue and NOK 96,000 in operating profit.

Key figures · 2024

Revenue
NOK 271,000
Operating profit
NOK 96,000
Equity
NOK 30,000
Est. value
NOK 252,000

Financial health · 2024

Liquidity
1.45
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
8.1%
Weak
Equity as a share of total capital

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

Who owns SYNSTEVASSÅSEN VANN OG AVLØP AS?

SYNSTEVASSÅSEN AS
SYNSTEVASSÅSEN VANN OG AVLØP AS
NOK 271,000 rev. · NOK 96,000 profit

SYNSTEVASSÅSEN VANN OG AVLØP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SYNSTEVASSÅSEN VANN OG AVLØP AS

Who owns SYNSTEVASSÅSEN VANN OG AVLØP AS?

SYNSTEVASSÅSEN AS is the largest registered owner, with 100.0%.

What is the revenue of SYNSTEVASSÅSEN VANN OG AVLØP AS?

SYNSTEVASSÅSEN VANN OG AVLØP AS had revenue of NOK 271,000 in 2024.

Where is SYNSTEVASSÅSEN VANN OG AVLØP AS based?

SYNSTEVASSÅSEN VANN OG AVLØP AS has its business address in Nesbyen.

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.