BIZTRAC BETA
General cleaning of buildings

ODDA RENHOLD AS

Org. no. 930764205 Limited company (AS) Ullensvang Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 34.2m
Operating profit NOK 6.8m
Equity NOK 2.1m
Incorporated 2023
Employees 10
Share capital NOK 200,000

ODDA RENHOLD AS is registered as a limited company in Ullensvang, Vestland with organisation number 930764205. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2023 and has 10 registered employees. Registered share capital is NOK 200,000, divided into 2000 shares. The company's stated purpose is: “Renhold av bygg og andre produkter, tjenester som naturlig hører sammen med dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 34.2m in revenue and NOK 6.8m in operating profit.

Key figures · 2024

Revenue
NOK 34.2m
Operating profit
NOK 6.8m
Equity
NOK 2.1m
Est. value
NOK 22.5m

Financial health · 2024

Liquidity
0.60
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
12.7%
Satisfactory
Equity as a share of total capital

Who owns ODDA RENHOLD AS?

ODDA SERVICE AS
ODDA RENHOLD AS
NOK 34.2m rev. · NOK 6.8m profit

ODDA RENHOLD AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ODDA RENHOLD AS

Who owns ODDA RENHOLD AS?

ODDA SERVICE AS is the largest registered owner, with 100.0%.

What is the revenue of ODDA RENHOLD AS?

ODDA RENHOLD AS had revenue of NOK 34.2m in 2024.

Who is the general manager of ODDA RENHOLD AS?

Kamil Piotr Hadrys is registered as general manager of ODDA RENHOLD AS.

Where is ODDA RENHOLD AS based?

ODDA RENHOLD AS has its business address in Odda.

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.