BIZTRAC BETA
General cleaning of buildings

LIVING CLEAN RENHOLD AS

Org. no. 997963164 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 82.4m
Operating profit NOK 5.6m
Equity NOK −11.6m
Incorporated 2012
Employees 368
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−11,6 mill kr).

LIVING CLEAN RENHOLD AS is registered as a limited company in Oslo, Oslo with organisation number 997963164. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2012 and has 368 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Renhold av næringseiendom det som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 82.4m in revenue and NOK 5.6m in operating profit.

Key figures · 2024

Revenue
NOK 82.4m
Operating profit
NOK 5.6m
Equity
NOK −11.6m
Est. value
NOK 45.8m

Financial health · 2024

Liquidity
0.49
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-47.8%
Weak
Equity as a share of total capital

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

Who owns LIVING CLEAN RENHOLD AS?

No shareholders are registered for LIVING CLEAN RENHOLD AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about LIVING CLEAN RENHOLD AS

What is the revenue of LIVING CLEAN RENHOLD AS?

LIVING CLEAN RENHOLD AS had revenue of NOK 82.4m in 2024.

Who is the general manager of LIVING CLEAN RENHOLD AS?

Geir Arne Reite Heggelund is registered as general manager of LIVING CLEAN RENHOLD AS.

Where is LIVING CLEAN RENHOLD AS based?

LIVING CLEAN RENHOLD AS has its business address in Oslo.

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.