BIZTRAC BETA
Technical testing and analysis

RH SERTIFISERING AS

Org. no. 915550398 Limited company (AS) Volda Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 2.1m
Operating profit NOK 568,000
Equity NOK 1.1m
Incorporated 2015
Share capital NOK 200,000

RH SERTIFISERING AS is registered as a limited company in Volda, Møre og Romsdal with organisation number 915550398. The business is classified under technical testing and analysis (NACE 71.200). The company was incorporated in 2015. Registered share capital is NOK 200,000, divided into 200 shares. The company's stated purpose is: “Kontroll og prosjektleiing av serviceoppdrag for kraner, også ved å delta i andre selskap med liknande verksemd, kjøp og sal av aksjar, eller på annan måte å delta i andre føretak.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.1m in revenue and NOK 568,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.1m
Operating profit
NOK 568,000
Equity
NOK 1.1m
Est. value
NOK 2.7m

Financial health · 2025

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

Who owns RH SERTIFISERING AS?

ROY ARE HOVDENAKK
RH SERTIFISERING AS
NOK 2.1m rev. · NOK 568,000 profit

RH SERTIFISERING AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RH SERTIFISERING AS

Who owns RH SERTIFISERING AS?

ROY ARE HOVDENAKK is the largest registered owner, with 100.0%.

What is the revenue of RH SERTIFISERING AS?

RH SERTIFISERING AS had revenue of NOK 2.1m in 2025.

Who is the general manager of RH SERTIFISERING AS?

Roy Are Hovdenakk is registered as general manager of RH SERTIFISERING AS.

Where is RH SERTIFISERING AS based?

RH SERTIFISERING AS has its business address in Volda.

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.