BIZTRAC BETA
Business and other management consultancy activities

CLEANVALLEY AS

Org. no. 828300652 Limited company (AS) Bærum Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −138,000
Equity NOK 3.7m
Incorporated 2021
Share capital NOK 30,000

Signals

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

CLEANVALLEY AS is registered as a limited company in Bærum, Akershus with organisation number 828300652. The business is classified under business and other management consultancy activities (NACE 70.200). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rådgivningsvirksomhet og salg av tjenester og varer i tilknytning til dette, deltagelse i annen virksomhet samt forvaltning av egen kapital.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −138,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −138,000
Equity
NOK 3.7m
Est. value
NOK 21.0m

Financial health · 2024

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

Who owns CLEANVALLEY AS?

STIAN ANDERSEN RENDAL
CLEANVALLEY AS
NOK 0 rev. · NOK −138,000 profit

CLEANVALLEY AS has 1 registered shareholder:

All shareholders and roles →

Which companies does CLEANVALLEY AS own?

CLEANVALLEY AS holds stakes in 5 companies:

See the full ownership structure →

Frequently asked questions about CLEANVALLEY AS

Who owns CLEANVALLEY AS?

STIAN ANDERSEN RENDAL is the largest registered owner, with 100.0%.

What is the revenue of CLEANVALLEY AS?

CLEANVALLEY AS had revenue of NOK 0 in 2024.

Where is CLEANVALLEY AS based?

CLEANVALLEY AS has its business address in Bekkestua.

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.