BIZTRAC BETA
General cleaning of buildings

FJELLREGIONEN RENHOLD AS

Org. no. 924513764 Limited company (AS) Røros Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 6.4m
Operating profit NOK 823,000
Equity NOK 1.5m
Incorporated 2020
Employees 24
Share capital NOK 30,000

FJELLREGIONEN RENHOLD AS is registered as a limited company in Røros, Trøndelag with organisation number 924513764. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2020 and has 24 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Renhold av private boliger og bedrifter, bilvask og bilpleie, samt det som naturlig faller inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.4m in revenue and NOK 823,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.4m
Operating profit
NOK 823,000
Equity
NOK 1.5m
Est. value
NOK 4.1m

Financial health · 2025

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

Who owns FJELLREGIONEN RENHOLD AS?

KUSHTRIM KRASNIQI
FJELLREGIONEN RENHOLD AS
NOK 6.4m rev. · NOK 823,000 profit

FJELLREGIONEN RENHOLD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about FJELLREGIONEN RENHOLD AS

Who owns FJELLREGIONEN RENHOLD AS?

KUSHTRIM KRASNIQI is the largest registered owner, with 50.0%.

What is the revenue of FJELLREGIONEN RENHOLD AS?

FJELLREGIONEN RENHOLD AS had revenue of NOK 6.4m in 2025.

Who is the general manager of FJELLREGIONEN RENHOLD AS?

Kushtrim Krasniqi is registered as general manager of FJELLREGIONEN RENHOLD AS.

Where is FJELLREGIONEN RENHOLD AS based?

FJELLREGIONEN RENHOLD AS has its business address in Røros.

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.