BIZTRAC BETA
Water collection, treatment and supply

SANDERSTØLEN VANNVERK AS

Org. no. 915257267 Limited company (AS) Drammen Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.5m
Operating profit NOK 337,000
Equity NOK 5.2m
Incorporated 2015
Share capital NOK 1.0m

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SANDERSTØLEN VANNVERK AS is registered as a limited company in Drammen, Buskerud with organisation number 915257267. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2015. Registered share capital is NOK 1.0m, divided into 1030000 shares. The company's stated purpose is: “Forvalte og drifte vann og avløpssystemer rundt Sanderstølen. Dette omfatter investeringer i nye anlegg og drift av eksisterende.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.5m in revenue and NOK 337,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.5m
Operating profit
NOK 337,000
Equity
NOK 5.2m
Est. value
NOK 4.1m

Financial health · 2024

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

Who owns SANDERSTØLEN VANNVERK AS?

SANDERSTØLEN HOLDING AS
SANDERSTØLEN VANNVERK AS
NOK 2.5m rev. · NOK 337,000 profit

SANDERSTØLEN VANNVERK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SANDERSTØLEN VANNVERK AS

Who owns SANDERSTØLEN VANNVERK AS?

SANDERSTØLEN HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SANDERSTØLEN VANNVERK AS?

SANDERSTØLEN VANNVERK AS had revenue of NOK 2.5m in 2024.

Where is SANDERSTØLEN VANNVERK AS based?

SANDERSTØLEN VANNVERK AS has its business address in Drammen.

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.