BIZTRAC BETA
Plumbing installation

HM RØR AS

Org. no. 996796507 Limited company (AS) Oslo Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 4.8m
Operating profit NOK 383,000
Equity NOK 698,000
Incorporated 2011
Share capital NOK 200,000

HM RØR AS is registered as a limited company in Oslo, Oslo with organisation number 996796507. The business is classified under plumbing installation (NACE 43.221). The company was incorporated in 2011. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Rørleggertjenester og andre tjenester og produkter som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagender samt kjøp, salg og utleie av fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.8m in revenue and NOK 383,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.8m
Operating profit
NOK 383,000
Equity
NOK 698,000
Est. value
NOK 1.4m

Financial health · 2024

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

Who owns HM RØR AS?

TOMAS HØIMYR
HM RØR AS
NOK 4.8m rev. · NOK 383,000 profit

HM RØR AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HM RØR AS own?

HM RØR AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HM RØR AS

Who owns HM RØR AS?

TOMAS HØIMYR is the largest registered owner, with 50.0%.

What is the revenue of HM RØR AS?

HM RØR AS had revenue of NOK 4.8m in 2024.

Who is the general manager of HM RØR AS?

Halvor Mellem is registered as general manager of HM RØR AS.

Where is HM RØR AS based?

HM RØR AS has its business address in Oslo.

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.