biztrac. BETA
COMPANY REGISTER PROFILE
929346823 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other technical consultancy

SMARTVATTEN AS

Org. no. 929346823 Limited company (AS) Larvik Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 22.1m
Operating profit NOK 1.5m
Equity NOK 1.3m
Incorporated 2022
Employees 9
Share capital NOK 30,000

SMARTVATTEN AS is registered as a limited company in Larvik, Vestfold with organisation number 929346823. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Tilby effektiv overvåkning av vannforbruk og vannlekkasje, vannmåling og spareløsning, samt analyse og rapporteringstjeneste i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.1m in revenue and NOK 1.5m in operating profit.

Key figures · 2025

Revenue
NOK 22.1m
▲ +311 %
Operating profit
NOK 1.5m
▲ +465 %
Equity
NOK 1.3m
▲ +1735 %
Est. value
NOK 10.9m

Financial health · 2025

Liquidity
1.43
Satisfactory
Current assets ÷ current liabilities
Profitability
17.6%
Very good
Return on total assets
Solidity
9.4%
Weak
Equity as a share of total capital

Who owns SMARTVATTEN AS?

SMARTVATTEN OY FI
SMARTVATTEN AS
NOK 22.1m rev. · NOK 1.5m profit

SMARTVATTEN AS has 1 registered shareholder:

  • SMARTVATTEN OY 100.0%
All shareholders and roles →

Group structure

SMARTVATTEN AS er morselskap for 1 datterselskap:

Frequently asked questions about SMARTVATTEN AS

Who owns SMARTVATTEN AS?

SMARTVATTEN OY is the largest registered owner, with 100.0%.

What is the revenue of SMARTVATTEN AS?

SMARTVATTEN AS had revenue of NOK 22.1m in 2025.

Where is SMARTVATTEN AS based?

SMARTVATTEN AS has its business address in Larvik.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.