BIZTRAC BETA
Intermediation service activities for specialised retail sale

RH KJØLESERVICE AS

Org. no. 931712152 Limited company (AS) Lørenskog Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 256,000
Operating profit NOK 2.1m
Equity NOK 3.8m
Incorporated 2023
Share capital NOK 30,000

RH KJØLESERVICE AS is registered as a limited company in Lørenskog, Akershus with organisation number 931712152. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “VVS arbeid, kjøp og salg av varmepumpeanlegg, samt tilhørende virksomhet. Bruktbilhandel/import, kjøp og salg samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 256,000 in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 256,000
Operating profit
NOK 2.1m
Equity
NOK 3.8m
Est. value
NOK 9.4m

Financial health · 2025

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

Who owns RH KJØLESERVICE AS?

RUNE WILLY HAGEN
RH KJØLESERVICE AS
NOK 256,000 rev. · NOK 2.1m profit

RH KJØLESERVICE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RH KJØLESERVICE AS

Who owns RH KJØLESERVICE AS?

RUNE WILLY HAGEN is the largest registered owner, with 100.0%.

What is the revenue of RH KJØLESERVICE AS?

RH KJØLESERVICE AS had revenue of NOK 256,000 in 2025.

Who is the general manager of RH KJØLESERVICE AS?

Rune Willy Hagen is registered as general manager of RH KJØLESERVICE AS.

Where is RH KJØLESERVICE AS based?

RH KJØLESERVICE AS has its business address in Rasta.

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.