BIZTRAC BETA
General cleaning of buildings

HAUGALAND RENGJØRINGSSERVICE AS

Org. no. 933472388 Limited company (AS) Haugesund Incorporated 1982 Active
Ownership graph ↗
Revenue 2025 NOK 12.5m
Operating profit NOK 2.0m
Equity NOK 5.6m
Incorporated 1982
Employees 19
Share capital NOK 100,000

HAUGALAND RENGJØRINGSSERVICE AS is registered as a limited company in Haugesund, Rogaland with organisation number 933472388. The business is classified under general cleaning of buildings (NACE 81.210). The company was incorporated in 1982 and has 19 registered employees. Registered share capital is NOK 100,000. The company's stated purpose is: “Rengjøringsbyrå, samt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 12.5m in revenue and NOK 2.0m in operating profit.

Key figures · 2025

Revenue
NOK 12.5m
Operating profit
NOK 2.0m
Equity
NOK 5.6m
Est. value
NOK 10.6m

Financial health · 2025

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

Who owns HAUGALAND RENGJØRINGSSERVICE AS?

BENTE GERHARD
HAUGALAND RENGJØRINGSSERVICE AS
NOK 12.5m rev. · NOK 2.0m profit

HAUGALAND RENGJØRINGSSERVICE AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about HAUGALAND RENGJØRINGSSERVICE AS

Who owns HAUGALAND RENGJØRINGSSERVICE AS?

BENTE GERHARD is the largest registered owner, with 60.0%.

What is the revenue of HAUGALAND RENGJØRINGSSERVICE AS?

HAUGALAND RENGJØRINGSSERVICE AS had revenue of NOK 12.5m in 2025.

Who is the general manager of HAUGALAND RENGJØRINGSSERVICE AS?

Bente Gerhard is registered as general manager of HAUGALAND RENGJØRINGSSERVICE AS.

Where is HAUGALAND RENGJØRINGSSERVICE AS based?

HAUGALAND RENGJØRINGSSERVICE AS has its business address in Haugesund.

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.