BIZTRAC BETA
Research and experimental development on natural sciences and engineering

CLEANGRIP AS

Org. no. 822673112 Limited company (AS) Kongsberg Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 73,000
Operating profit NOK −161,000
Equity NOK −361,000
Incorporated 2019
Share capital NOK 52,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−361k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−161k kr).

CLEANGRIP AS is registered as a limited company in Kongsberg, Buskerud with organisation number 822673112. The business is classified under research and experimental development on natural sciences and engineering (NACE 72.100). The company was incorporated in 2019. Registered share capital is NOK 52,000, divided into 51672 shares. The company's stated purpose is: “Produktutvikling, samt eie og forvalte patentrettigheter. Produksjon, bearbeiding og salg av produkter.”. The most recent filed accounts, for the 2024 financial year, show NOK 73,000 in revenue and NOK −161,000 in operating profit.

Key figures · 2024

Revenue
NOK 73,000
Operating profit
NOK −161,000
Equity
NOK −361,000

Financial health · 2024

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

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

Who owns CLEANGRIP AS?

TIT HOLDING AS
CLEANGRIP AS
NOK 73,000 rev. · NOK −161,000 profit

CLEANGRIP AS has 8 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLEANGRIP AS

Who owns CLEANGRIP AS?

TIT HOLDING AS is the largest registered owner, with 34.1%.

What is the revenue of CLEANGRIP AS?

CLEANGRIP AS had revenue of NOK 73,000 in 2024.

Where is CLEANGRIP AS based?

CLEANGRIP AS has its business address in Kongsberg.

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.