BIZTRAC BETA
Water collection, treatment and supply

NAVERFJORDEN VANN OG AVLØP AS

Org. no. 918858245 Limited company (AS) Tønsberg Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 65,000
Operating profit NOK −7,000
Equity NOK 107,000
Incorporated 2017
Share capital NOK 50,000

Signals

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

NAVERFJORDEN VANN OG AVLØP AS is registered as a limited company in Tønsberg, Vestfold with organisation number 918858245. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2017. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Eie og drive anlegg for håndtering av vann og avløp, samt alt som står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 65,000 in revenue and NOK −7,000 in operating profit.

Key figures · 2025

Revenue
NOK 65,000
Operating profit
NOK −7,000
Equity
NOK 107,000
Est. value
NOK 107,000

Financial health · 2025

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

Who owns NAVERFJORDEN VANN OG AVLØP AS?

MARKESTRANDA & OMEGN VANNLAG SA
NAVERFJORDEN VANN OG AVLØP AS
NOK 65,000 rev. · NOK −7,000 profit

NAVERFJORDEN VANN OG AVLØP AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about NAVERFJORDEN VANN OG AVLØP AS

Who owns NAVERFJORDEN VANN OG AVLØP AS?

MARKESTRANDA & OMEGN VANNLAG SA is the largest registered owner, with 50.0%.

What is the revenue of NAVERFJORDEN VANN OG AVLØP AS?

NAVERFJORDEN VANN OG AVLØP AS had revenue of NOK 65,000 in 2025.

Where is NAVERFJORDEN VANN OG AVLØP AS based?

NAVERFJORDEN VANN OG AVLØP AS has its business address in Tønsberg.

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.