BIZTRAC BETA
Leasing of intellectual property and similar products, except copyrighted works

WATERISE TECHNOLOGIES AS

Org. no. 934159144 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −1,000
Equity NOK 23,000
Incorporated 2024
Share capital NOK 75,000

Signals

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

WATERISE TECHNOLOGIES AS is registered as a limited company in Oslo, Oslo with organisation number 934159144. The business is classified under leasing of intellectual property and similar products, except copyrighted works (NACE 77.400). The company was incorporated in 2024. Registered share capital is NOK 75,000, divided into 30000 shares. The company's stated purpose is: “Å eie og forvalte konsernets patenter og immaterielle rettigheter, samt det som står i naturlig forbindelse med dette.”.

Key figures · 2024

Operating profit
NOK −1,000
Equity
NOK 23,000
Est. value
NOK 33,000

Financial health · 2024

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

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

Who owns WATERISE TECHNOLOGIES AS?

WATERISE B.V.
WATERISE TECHNOLOGIES AS
· NOK −1,000 profit

WATERISE TECHNOLOGIES AS has 1 registered shareholder:

All shareholders and roles →

Group structure

WATERISE TECHNOLOGIES AS er morselskap for 2 datterselskaper:

Frequently asked questions about WATERISE TECHNOLOGIES AS

Who owns WATERISE TECHNOLOGIES AS?

WATERISE B.V. is the largest registered owner, with 100.0%.

Who is the general manager of WATERISE TECHNOLOGIES AS?

Niels Petter Wright is registered as general manager of WATERISE TECHNOLOGIES AS.

Where is WATERISE TECHNOLOGIES AS based?

WATERISE TECHNOLOGIES AS has its business address in Oslo.

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.