BIZTRAC BETA
Wholesale of china and glassware and cleaning materials

CLEANING AS

Org. no. 928131378 Limited company (AS) Bergen Incorporated 2021 Active
Ownership graph ↗
Revenue 2024 NOK 51,000
Operating profit NOK −117,000
Equity NOK 84,000
Incorporated 2021
Share capital NOK 230,000

Signals

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

CLEANING AS is registered as a limited company in Bergen, Vestland with organisation number 928131378. The business is classified under wholesale of china and glassware and cleaning materials (NACE 46.440). The company was incorporated in 2021. Registered share capital is NOK 230,000, divided into 2300 shares. The company's stated purpose is: “Import og salg av hygiene- og rengjøringsprodukter, samt kursvirksomhet relater til renhold.”. The most recent filed accounts, for the 2024 financial year, show NOK 51,000 in revenue and NOK −117,000 in operating profit.

Key figures · 2024

Revenue
NOK 51,000
Operating profit
NOK −117,000
Equity
NOK 84,000
Est. value
NOK 105,000

Financial health · 2024

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

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

Who owns CLEANING AS?

TROND LOUIS HUSBY
CLEANING AS
NOK 51,000 rev. · NOK −117,000 profit

CLEANING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CLEANING AS

Who owns CLEANING AS?

TROND LOUIS HUSBY is the largest registered owner, with 100.0%.

What is the revenue of CLEANING AS?

CLEANING AS had revenue of NOK 51,000 in 2024.

Who is the general manager of CLEANING AS?

Trond Louis Husby is registered as general manager of CLEANING AS.

Where is CLEANING AS based?

CLEANING AS has its business address in Straumsgrend.

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.