BIZTRAC BETA
General cleaning of buildings

BERGSTADEN RENGJØRING AS

Org. no. 927817357 Limited company (AS) Røros Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 4.8m
Operating profit NOK 1.0m
Equity NOK 448,000
Incorporated 2021
Employees 17
Share capital NOK 150,000

BERGSTADEN RENGJØRING AS is registered as a limited company in Røros, Trøndelag with organisation number 927817357. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 2021 and has 17 registered employees. Registered share capital is NOK 150,000, divided into 150 shares. The company's stated purpose is: “Renholdstjenester av næringsbygg, hus og leiligheter samt all annen naturlig aktivitet som faller inn under denne bransjen.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.8m in revenue and NOK 1.0m in operating profit.

Key figures · 2025

Revenue
NOK 4.8m
Operating profit
NOK 1.0m
Equity
NOK 448,000
Est. value
NOK 3.3m

Financial health · 2024

Liquidity
1.30
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
21.9%
Good
Equity as a share of total capital

Who owns BERGSTADEN RENGJØRING AS?

CHRISTOFFER LAUGEN
BERGSTADEN RENGJØRING AS
NOK 4.8m rev. · NOK 1.0m profit

BERGSTADEN RENGJØRING AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about BERGSTADEN RENGJØRING AS

Who owns BERGSTADEN RENGJØRING AS?

CHRISTOFFER LAUGEN is the largest registered owner, with 33.3%.

What is the revenue of BERGSTADEN RENGJØRING AS?

BERGSTADEN RENGJØRING AS had revenue of NOK 4.8m in 2025.

Who is the general manager of BERGSTADEN RENGJØRING AS?

Christoffer Laugen is registered as general manager of BERGSTADEN RENGJØRING AS.

Where is BERGSTADEN RENGJØRING AS based?

BERGSTADEN RENGJØRING 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.