biztrac. BETA
COMPANY REGISTER PROFILE
926677918 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Washing and cleaning of textile and fur products

RØYKEN RENS AS

Org. no. 926677918 Limited company (AS) Asker Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 2.7m
Operating profit NOK −30,000
Equity NOK 239,000
Incorporated 2021
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−30k kr).

RØYKEN RENS AS is registered as a limited company in Asker, Akershus with organisation number 926677918. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Rens, skredderservice, skoreparasjon og nøkkelfylling.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.7m in revenue and NOK −30,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.7m
▲ +2 %
Operating profit
NOK −30,000
▼ −96 %
Equity
NOK 239,000
▼ −12 %
Est. value
NOK 144,000

Financial health · 2025

Liquidity
1.09
Satisfactory
Current assets ÷ current liabilities
Profitability
-2.8%
Not satisfactory
Return on total assets
Solidity
28.6%
Good
Equity as a share of total capital

Who owns RØYKEN RENS AS?

RØYKEN RENS AS
NOK 2.7m rev. · NOK −30,000 profit

RØYKEN RENS AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about RØYKEN RENS AS

Who owns RØYKEN RENS AS?

Maryam Ibrahimi is the largest registered owner, with 50.0%.

What is the revenue of RØYKEN RENS AS?

RØYKEN RENS AS had revenue of NOK 2.7m in 2025.

Who is the general manager of RØYKEN RENS AS?

Ali Reza Hassani is registered as general manager of RØYKEN RENS AS.

Where is RØYKEN RENS AS based?

RØYKEN RENS AS has its business address in Slemmestad.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.