BIZTRAC BETA
General cleaning of buildings

RENAS BEDRIFT AS

Org. no. 970967583 Limited company (AS) Lillestrøm Incorporated 1994 Active
Ownership graph ↗
Revenue 2024 NOK 6.8m
Operating profit NOK −69,000
Equity NOK 2.0m
Incorporated 1994
Employees 23
Share capital NOK 200,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−69k kr).

RENAS BEDRIFT AS is registered as a limited company in Lillestrøm, Akershus with organisation number 970967583. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 1994 and has 23 registered employees. Registered share capital is NOK 200,000, divided into 50 shares. The company's stated purpose is: “Salg og levering av renholdstjenester, samt hva hermed står i forbindelse, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 6.8m in revenue and NOK −69,000 in operating profit.

Key figures · 2024

Revenue
NOK 6.8m
Operating profit
NOK −69,000
Equity
NOK 2.0m
Est. value
NOK 3.1m

Financial health · 2024

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

Who owns RENAS BEDRIFT AS?

AGNES INVEST AS
RENAS BEDRIFT AS
NOK 6.8m rev. · NOK −69,000 profit

RENAS BEDRIFT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RENAS BEDRIFT AS

Who owns RENAS BEDRIFT AS?

AGNES INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of RENAS BEDRIFT AS?

RENAS BEDRIFT AS had revenue of NOK 6.8m in 2024.

Who is the general manager of RENAS BEDRIFT AS?

Suthan Kanavathi is registered as general manager of RENAS BEDRIFT AS.

Where is RENAS BEDRIFT AS based?

RENAS BEDRIFT AS has its business address in Strømmen.

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.