BIZTRAC BETA
General cleaning of buildings

RENHOLDSBYRÅET AS

Org. no. 919627484 Limited company (AS) Oslo Incorporated 2017 Active
Ownership graph ↗
Revenue 2025 NOK 3.9m
Operating profit NOK 470,000
Equity NOK 76,000
Incorporated 2017
Share capital NOK 30,000

Signals

1 flags
  • Nylig endring 2026-04-08 Adresseendring registrert 2026-04-08.

RENHOLDSBYRÅET AS is registered as a limited company in Oslo, Oslo with organisation number 919627484. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2017. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Rengjøring av kontorer og boliger og det som har tilknytning til dette, samt deltagelse i andre selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 3.9m in revenue and NOK 470,000 in operating profit.

Key figures · 2025

Revenue
NOK 3.9m
Operating profit
NOK 470,000
Equity
NOK 76,000
Est. value
NOK 2.0m

Financial health · 2025

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

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

Who owns RENHOLDSBYRÅET AS?

KAROLINA SZYSZKO
RENHOLDSBYRÅET AS
NOK 3.9m rev. · NOK 470,000 profit

RENHOLDSBYRÅET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RENHOLDSBYRÅET AS

Who owns RENHOLDSBYRÅET AS?

KAROLINA SZYSZKO is the largest registered owner, with 50.0%.

What is the revenue of RENHOLDSBYRÅET AS?

RENHOLDSBYRÅET AS had revenue of NOK 3.9m in 2025.

Who is the general manager of RENHOLDSBYRÅET AS?

Karolina Szyszko is registered as general manager of RENHOLDSBYRÅET AS.

Where is RENHOLDSBYRÅET AS based?

RENHOLDSBYRÅET 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.