BIZTRAC BETA
Washing and cleaning of textile and fur products

VOLVAT RENS AS

Org. no. 921041225 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK −64,000
Equity NOK 19,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

VOLVAT RENS AS is registered as a limited company in Oslo, Oslo with organisation number 921041225. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Skredderi, klesreparasjon, vaskeri- og renserivirksomhet og andre produkter/tjenester som naturlig hører sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK −64,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK −64,000
Equity
NOK 19,000
Est. value
NOK 795,000

Financial health · 2025

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

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

Who owns VOLVAT RENS AS?

RAHMAT AHMADI
VOLVAT RENS AS
NOK 1.1m rev. · NOK −64,000 profit

VOLVAT RENS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VOLVAT RENS AS

Who owns VOLVAT RENS AS?

RAHMAT AHMADI is the largest registered owner, with 100.0%.

What is the revenue of VOLVAT RENS AS?

VOLVAT RENS AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VOLVAT RENS AS?

Rahmat Ahmadi is registered as general manager of VOLVAT RENS AS.

Where is VOLVAT RENS AS based?

VOLVAT RENS 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.