BIZTRAC BETA
Joinery installation

RH VEDLIKEHOLD AS

Org. no. 915605532 Limited company (AS) Tjeldsund Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 130,000
Operating profit NOK 57,000
Equity NOK 17.7m
Incorporated 2015
Share capital NOK 30,000

RH VEDLIKEHOLD AS is registered as a limited company in Tjeldsund, Troms with organisation number 915605532. The business is classified under joinery installation (NACE 43.320). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Snekker-, maler og renoveringsarbeid samt hva herunder tilhører og kunne delta i annen virksomhet med økonomisk formål.”. The most recent filed accounts, for the 2025 financial year, show NOK 130,000 in revenue and NOK 57,000 in operating profit.

Key figures · 2025

Revenue
NOK 130,000
Operating profit
NOK 57,000
Equity
NOK 17.7m
Est. value
NOK 7.8m

Financial health · 2024

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

Who owns RH VEDLIKEHOLD AS?

RUNE HERMANN HJELMSØ
RH VEDLIKEHOLD AS
NOK 130,000 rev. · NOK 57,000 profit

RH VEDLIKEHOLD AS has 1 registered shareholder:

All shareholders and roles →

Which companies does RH VEDLIKEHOLD AS own?

RH VEDLIKEHOLD AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about RH VEDLIKEHOLD AS

Who owns RH VEDLIKEHOLD AS?

RUNE HERMANN HJELMSØ is the largest registered owner, with 100.0%.

What is the revenue of RH VEDLIKEHOLD AS?

RH VEDLIKEHOLD AS had revenue of NOK 130,000 in 2025.

Who is the general manager of RH VEDLIKEHOLD AS?

Rune Hermann Hjelmsø is registered as general manager of RH VEDLIKEHOLD AS.

Where is RH VEDLIKEHOLD AS based?

RH VEDLIKEHOLD AS has its business address in Evenskjer.

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.