BIZTRAC BETA
Other cleaning activities

RENTOX AS

Org. no. 924576820 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 22.4m
Operating profit NOK 2.9m
Equity NOK 3.2m
Incorporated 2020
Employees 15
Share capital NOK 50,000

RENTOX AS is registered as a limited company in Bergen, Vestland with organisation number 924576820. The business is classified under other cleaning activities (NACE 81.230). The company was incorporated in 2020 and has 15 registered employees. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Skadedyrkontroll og bekjempelse av skadedyr, hussoppkontroll, muggsoppkontroll og sanering, samt utbedring av bygningskader, droneinspeksjoner av takkonstruksjoner, meglertakster skadedyr, leveranse og montering av avfuktingsanlegg og det som herunder faller naturlig.”. The most recent filed accounts, for the 2025 financial year, show NOK 22.4m in revenue and NOK 2.9m in operating profit.

Key figures · 2025

Revenue
NOK 22.4m
Operating profit
NOK 2.9m
Equity
NOK 3.2m
Est. value
NOK 13.2m

Financial health · 2025

Liquidity
1.49
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
36.6%
Good
Equity as a share of total capital

Who owns RENTOX AS?

RENTOX HOLDING AS
RENTOX AS
NOK 22.4m rev. · NOK 2.9m profit

RENTOX AS has 1 registered shareholder:

All shareholders and roles →

Group structure

RENTOX AS er morselskap for 1 datterselskap:

Frequently asked questions about RENTOX AS

Who owns RENTOX AS?

RENTOX HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of RENTOX AS?

RENTOX AS had revenue of NOK 22.4m in 2025.

Who is the general manager of RENTOX AS?

Stian Sletten Erdal is registered as general manager of RENTOX AS.

Where is RENTOX AS based?

RENTOX AS has its business address in Arnatveit.

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.