BIZTRAC BETA
Water collection, treatment and supply

MØLNELVA VANNVERK AS

Org. no. 921172109 Limited company (AS) Tjeldsund Incorporated 2018 Active
Ownership graph ↗
Revenue 2024 NOK 98,000
Operating profit NOK −41,000
Equity NOK 148,000
Incorporated 2018
Share capital NOK 110,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−41k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

MØLNELVA VANNVERK AS is registered as a limited company in Tjeldsund, Troms with organisation number 921172109. The business is classified under water collection, treatment and supply (NACE 36.000). The company was incorporated in 2018. Registered share capital is NOK 110,000, divided into 48 shares. The company's stated purpose is: “Eie og drive et vannverk som leverer vann til aksjonærene og andre abonnenter.”. The most recent filed accounts, for the 2024 financial year, show NOK 98,000 in revenue and NOK −41,000 in operating profit.

Key figures · 2024

Revenue
NOK 98,000
Operating profit
NOK −41,000
Equity
NOK 148,000
Est. value
NOK 153,000

Financial health · 2024

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

Who owns MØLNELVA VANNVERK AS?

GROVFJORD INDUSTRIER AS
MØLNELVA VANNVERK AS
NOK 98,000 rev. · NOK −41,000 profit

MØLNELVA VANNVERK AS has 12 registered shareholders:

All shareholders and roles →

Frequently asked questions about MØLNELVA VANNVERK AS

Who owns MØLNELVA VANNVERK AS?

GROVFJORD INDUSTRIER AS is the largest registered owner, with 54.2%.

What is the revenue of MØLNELVA VANNVERK AS?

MØLNELVA VANNVERK AS had revenue of NOK 98,000 in 2024.

Where is MØLNELVA VANNVERK AS based?

MØLNELVA VANNVERK AS has its business address in Grovfjord.

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.