BIZTRAC BETA
Computer programming activities

VANNHUB AS

Org. no. 934179307 Limited company (AS) Vestby Incorporated 2024 Active
Ownership graph ↗
Revenue 2025 NOK 286,000
Operating profit NOK −143,000
Equity NOK −56,000
Incorporated 2024
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−56k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−143k kr).

VANNHUB AS is registered as a limited company in Vestby, Akershus with organisation number 934179307. The business is classified under computer programming activities (NACE 62.100). The company was incorporated in 2024. Registered share capital is NOK 30,000, divided into 100000 shares. The company's stated purpose is: “Utvikling av sensorer, instrumenter, programvare og tjenester knyttet til vann og avløp.”. The most recent filed accounts, for the 2025 financial year, show NOK 286,000 in revenue and NOK −143,000 in operating profit.

Key figures · 2025

Revenue
NOK 286,000
Operating profit
NOK −143,000
Equity
NOK −56,000

Financial health · 2025

Liquidity
0.28
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-329.6%
Weak
Equity as a share of total capital

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

Who owns VANNHUB AS?

OLAV MØLL FRENGSTAD
VANNHUB AS
NOK 286,000 rev. · NOK −143,000 profit

VANNHUB AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VANNHUB AS

Who owns VANNHUB AS?

OLAV MØLL FRENGSTAD is the largest registered owner, with 100.0%.

What is the revenue of VANNHUB AS?

VANNHUB AS had revenue of NOK 286,000 in 2025.

Who is the general manager of VANNHUB AS?

Olav Møll Frengstad is registered as general manager of VANNHUB AS.

Where is VANNHUB AS based?

VANNHUB AS has its business address in Hvitsten.

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.