BIZTRAC BETA
Washing and cleaning of textile and fur products

RENSERISERVICE AS

Org. no. 894566612 Limited company (AS) Ringsaker Incorporated 2009 Active
Ownership graph ↗
Revenue 2024 NOK 7.8m
Operating profit NOK 199,000
Equity NOK 369,000
Incorporated 2009
Employees 16
Share capital NOK 100,000

RENSERISERVICE AS is registered as a limited company in Ringsaker, Innlandet with organisation number 894566612. The business is classified under washing and cleaning of textile and fur products (NACE 96.100). The company was incorporated in 2009 and has 16 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Vask og rens av tekstiler.”. The most recent filed accounts, for the 2024 financial year, show NOK 7.8m in revenue and NOK 199,000 in operating profit.

Key figures · 2024

Revenue
NOK 7.8m
Operating profit
NOK 199,000
Equity
NOK 369,000
Est. value
NOK 943,000

Financial health · 2024

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

Who owns RENSERISERVICE AS?

OLE-JACOB BREIMO
RENSERISERVICE AS
NOK 7.8m rev. · NOK 199,000 profit

RENSERISERVICE AS has 2 registered shareholders:

All shareholders and roles →

Which companies does RENSERISERVICE AS own?

RENSERISERVICE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about RENSERISERVICE AS

Who owns RENSERISERVICE AS?

OLE-JACOB BREIMO is the largest registered owner, with 67.0%.

What is the revenue of RENSERISERVICE AS?

RENSERISERVICE AS had revenue of NOK 7.8m in 2024.

Who is the general manager of RENSERISERVICE AS?

Anne Beate Andersen is registered as general manager of RENSERISERVICE AS.

Where is RENSERISERVICE AS based?

RENSERISERVICE AS has its business address in Brumunddal.

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.