BIZTRAC BETA
COMPANY REGISTER PROFILE
986441948 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 02.09.2026
Wholesale of other machinery and equipment

CLEANPRO AS

Org. no. 986441948 Limited company (AS) Lillestrøm Incorporated 2004 Active
Ownership graph ↗
Revenue 2025 NOK 30.4m
Operating profit NOK 3.6m
Equity NOK 6.9m
Incorporated 2004
Employees 7
Share capital NOK 500,000

CLEANPRO AS is registered as a limited company in Lillestrøm, Akershus with organisation number 986441948. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2004 and has 7 registered employees. Registered share capital is NOK 500,000, divided into 500 shares. The company's stated purpose is: “Service virksomhet spesielt rettet mot industrielt renhold, herunder import, kjøp og salg av deler og utstyr. Selskapet skal også kunne være medeier i andre selskap samt investere i andre typer virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 30.4m in revenue and NOK 3.6m in operating profit.

Key figures · 2025

Revenue
NOK 30.4m
▲ +11 %
Operating profit
NOK 3.6m
▲ +10 %
Equity
NOK 6.9m
▲ +9 %
Est. value
NOK 15.0m

Financial health · 2025

Liquidity
1.82
Good
Current assets ÷ current liabilities
Profitability
29.1%
Very good
Return on total assets
Solidity
47.5%
Very good
Equity as a share of total capital

Who owns CLEANPRO AS?

CLEANPRO AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about CLEANPRO AS

Who owns CLEANPRO AS?

BKR HOLDING AS is the largest registered owner, with 41.6%.

What is the revenue of CLEANPRO AS?

CLEANPRO AS had revenue of NOK 30.4m in 2025.

Who is the general manager of CLEANPRO AS?

Børre Kristoffersen is registered as general manager of CLEANPRO AS.

Where is CLEANPRO AS based?

CLEANPRO AS has its business address in Frogner.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 02.09.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.