BIZTRAC BETA
Water collection, treatment and supply

LAUVÅS VANN OG AVLØP AS

Org. no. 918461698 Limited company (AS) Sola Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 107,000
Operating profit NOK −150,000
Equity NOK 576,000
Incorporated 2017
Share capital NOK 1.7m

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−150k kr).

LAUVÅS VANN OG AVLØP AS is registered as a limited company in Sola, Rogaland with organisation number 918461698. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2017. Registered share capital is NOK 1.7m, divided into 1150 shares. The company's stated purpose is: “Anskaffelse, drift og vedlikehold av anlegg for vann og kloakk til boliger og fritidsboliger på Lauvås i Sandnes Kommune, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 107,000 in revenue and NOK −150,000 in operating profit.

Key figures · 2025

Revenue
NOK 107,000
Operating profit
NOK −150,000
Equity
NOK 576,000
Est. value
NOK 422,000

Financial health · 2025

Liquidity
4.87
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
17.5%
Satisfactory
Equity as a share of total capital

Who owns LAUVÅS VANN OG AVLØP AS?

ODDBJØRN TUNHEIM
LAUVÅS VANN OG AVLØP AS
NOK 107,000 rev. · NOK −150,000 profit

LAUVÅS VANN OG AVLØP AS has 20+ registered shareholders:

All shareholders and roles →

Frequently asked questions about LAUVÅS VANN OG AVLØP AS

Who owns LAUVÅS VANN OG AVLØP AS?

ODDBJØRN TUNHEIM is the largest registered owner, with 8.0%.

What is the revenue of LAUVÅS VANN OG AVLØP AS?

LAUVÅS VANN OG AVLØP AS had revenue of NOK 107,000 in 2025.

Where is LAUVÅS VANN OG AVLØP AS based?

LAUVÅS VANN OG AVLØP AS has its business address in Tananger.

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.