BIZTRAC BETA
Sewerage

VEAS AS

Org. no. 920171400 Limited company (AS) Asker Incorporated 2017 Active
Ownership graph ↗
Revenue 2024 NOK 6.0m
Operating profit NOK −275,000
Equity NOK 730.4m
Incorporated 2017
Share capital NOK 210.0m

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−275k kr).

VEAS AS is registered as a limited company in Asker, Akershus with organisation number 920171400. The business is classified under sewerage (NACE 37.000). The company was incorporated in 2017. Registered share capital is NOK 210.0m, divided into 30000 shares. The company's stated purpose is: “Veas AS skal eie og forvalte datterselskapene i konsernet, som blant annet renser vann og selger produkter og tjenester til beste for miljøet, samfunnet og en bærekraftig sirkulær økonomi. Veas skal minimere forurensende utslipp, skape verdier og være en god samfunnsaktør.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.0m in revenue and NOK −275,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.0m
Operating profit
NOK −275,000
Equity
NOK 730.4m
Est. value
NOK 452.3m

Financial health · 2024

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

Who owns VEAS AS?

OSLO KOMMUNE VANN- OG AVLØPSETATEN
VEAS AS
NOK 6.0m rev. · NOK −275,000 profit

VEAS AS has 3 registered shareholders:

All shareholders and roles →

Which companies does VEAS AS own?

VEAS AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about VEAS AS

Who owns VEAS AS?

OSLO KOMMUNE VANN- OG AVLØPSETATEN is the largest registered owner, with 70.5%.

What is the revenue of VEAS AS?

VEAS AS had revenue of NOK 6.0m in 2024.

Where is VEAS AS based?

VEAS AS has its business address in Slemmestad.

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.