BIZTRAC BETA
Wholesale of other machinery and equipment

DYNAMIC CLEANING TECHNOLOGY AS

Org. no. 929978374 Limited company (AS) Sola Incorporated 2022 Active
Ownership graph ↗
Revenue 2024 NOK 5.2m
Operating profit NOK 1.4m
Equity NOK 7.7m
Incorporated 2022
Share capital NOK 120,000

DYNAMIC CLEANING TECHNOLOGY AS is registered as a limited company in Sola, Rogaland with organisation number 929978374. The business is classified under wholesale of other machinery and equipment (NACE 46.640). The company was incorporated in 2022. Registered share capital is NOK 120,000, divided into 1000 shares. The company's stated purpose is: “Salg og utleie av utstyr og konsulenttjenester vedrørende automatisk rengjøring av tankanlegg, samt vaskevannsresirkulering/rensing og annet som naturlig faller sammen med dette relatert til oljebransjen og landindustrien.”. The most recent filed accounts, for the 2024 financial year, show NOK 5.2m in revenue and NOK 1.4m in operating profit.

Key figures · 2024

Revenue
NOK 5.2m
Operating profit
NOK 1.4m
Equity
NOK 7.7m
Est. value
NOK 7.8m

Financial health · 2024

Liquidity
6.09
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
39.3%
Good
Equity as a share of total capital

Who owns DYNAMIC CLEANING TECHNOLOGY AS?

FRANK ECOS AS
DYNAMIC CLEANING TECHNOLOGY AS
NOK 5.2m rev. · NOK 1.4m profit

DYNAMIC CLEANING TECHNOLOGY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DYNAMIC CLEANING TECHNOLOGY AS

Who owns DYNAMIC CLEANING TECHNOLOGY AS?

FRANK ECOS AS is the largest registered owner, with 50.0%.

What is the revenue of DYNAMIC CLEANING TECHNOLOGY AS?

DYNAMIC CLEANING TECHNOLOGY AS had revenue of NOK 5.2m in 2024.

Where is DYNAMIC CLEANING TECHNOLOGY AS based?

DYNAMIC CLEANING TECHNOLOGY AS has its business address in Tananger.

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.