BIZTRAC BETA
General cleaning of buildings

REN START RENHOLD AS

Org. no. 832748552 Limited company (AS) Ringerike Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 91,000
Equity NOK 172,000
Incorporated 2023
Employees 5
Share capital NOK 30,000

REN START RENHOLD AS is registered as a limited company in Ringerike, Buskerud with organisation number 832748552. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023 and has 5 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen innvendig rengjøring og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 91,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 91,000
Equity
NOK 172,000
Est. value
NOK 473,000

Financial health · 2025

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

Who owns REN START RENHOLD AS?

SELVARANI ANTHONY
REN START RENHOLD AS
NOK 1.1m rev. · NOK 91,000 profit

REN START RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about REN START RENHOLD AS

Who owns REN START RENHOLD AS?

SELVARANI ANTHONY is the largest registered owner, with 100.0%.

What is the revenue of REN START RENHOLD AS?

REN START RENHOLD AS had revenue of NOK 1.1m in 2025.

Who is the general manager of REN START RENHOLD AS?

Selvarani Anthony is registered as general manager of REN START RENHOLD AS.

Where is REN START RENHOLD AS based?

REN START RENHOLD AS has its business address in Hønefoss.

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.