BIZTRAC BETA
Other technical consultancy

CLEAN INDUSTRIAL SOLUTIONS AS

Org. no. 930087882 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 202,000
Operating profit NOK 148,000
Equity NOK 44,000
Incorporated 2022
Share capital NOK 30,000

CLEAN INDUSTRIAL SOLUTIONS AS is registered as a limited company in Oslo, Oslo with organisation number 930087882. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å drive med utvikling av prosjekter innen kjemi og energi, samt eie av egenutviklet teknologi innen kjemi og energibransjen. Selskapet skal også ha deltakelse i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 202,000 in revenue and NOK 148,000 in operating profit.

Key figures · 2024

Revenue
NOK 202,000
Operating profit
NOK 148,000
Equity
NOK 44,000
Est. value
NOK 440,000

Financial health · 2024

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

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

Who owns CLEAN INDUSTRIAL SOLUTIONS AS?

PS CARRERA AB
CLEAN INDUSTRIAL SOLUTIONS AS
NOK 202,000 rev. · NOK 148,000 profit

CLEAN INDUSTRIAL SOLUTIONS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLEAN INDUSTRIAL SOLUTIONS AS

Who owns CLEAN INDUSTRIAL SOLUTIONS AS?

PS CARRERA AB is the largest registered owner, with 50.0%.

What is the revenue of CLEAN INDUSTRIAL SOLUTIONS AS?

CLEAN INDUSTRIAL SOLUTIONS AS had revenue of NOK 202,000 in 2024.

Where is CLEAN INDUSTRIAL SOLUTIONS AS based?

CLEAN INDUSTRIAL SOLUTIONS 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.