BIZTRAC BETA
Other technical consultancy

CLEAN METAL PROCESSES AS

Org. no. 998628172 Limited company (AS) Gjøvik Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 392,000
Operating profit NOK 91,000
Equity NOK 74,000
Incorporated 2012
Share capital NOK 230,000

CLEAN METAL PROCESSES AS is registered as a limited company in Gjøvik, Innlandet with organisation number 998628172. The business is classified under other technical consultancy (NACE 71.129). The company was incorporated in 2012. Registered share capital is NOK 230,000, divided into 230000 shares. The company's stated purpose is: “Utvikling av metallurgiske prosesser og eierskap i konsepter relatert til metallbehandling.”. The most recent filed accounts, for the 2024 financial year, show NOK 392,000 in revenue and NOK 91,000 in operating profit.

Key figures · 2024

Revenue
NOK 392,000
Operating profit
NOK 91,000
Equity
NOK 74,000
Est. value
NOK 344,000

Financial health · 2024

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

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

Who owns CLEAN METAL PROCESSES AS?

AAM TECH HOLDING AS
CLEAN METAL PROCESSES AS
NOK 392,000 rev. · NOK 91,000 profit

CLEAN METAL PROCESSES AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLEAN METAL PROCESSES AS

Who owns CLEAN METAL PROCESSES AS?

AAM TECH HOLDING AS is the largest registered owner, with 95.8%.

What is the revenue of CLEAN METAL PROCESSES AS?

CLEAN METAL PROCESSES AS had revenue of NOK 392,000 in 2024.

Who is the general manager of CLEAN METAL PROCESSES AS?

Ådne Midtlin is registered as general manager of CLEAN METAL PROCESSES AS.

Where is CLEAN METAL PROCESSES AS based?

CLEAN METAL PROCESSES AS has its business address in Gjøvik.

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.