BIZTRAC BETA
Manufacture of luggage, handbags, saddlery and harness of any material

RHJ AS

Org. no. 997543157 Limited company (AS) Rakkestad Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 11.1m
Operating profit NOK 552,000
Equity NOK 466,000
Incorporated 2011
Employees 9
Share capital NOK 100,000

RHJ AS is registered as a limited company in Rakkestad, Østfold with organisation number 997543157. The business is classified under manufacture of luggage, handbags, saddlery and harness of any material (NACE 15.120). The company was incorporated in 2011 and has 9 registered employees. Registered share capital is NOK 100,000, divided into 1000 shares. The company's stated purpose is: “Produksjon av båtkalesjer, industrisøm, salmakerartikler og andre produkter/tjenester som naturlig hører sammen med dette, herunder delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak.”. The most recent filed accounts, for the 2024 financial year, show NOK 11.1m in revenue and NOK 552,000 in operating profit.

Key figures · 2024

Revenue
NOK 11.1m
Operating profit
NOK 552,000
Equity
NOK 466,000
Est. value
NOK 1.8m

Financial health · 2024

Liquidity
0.92
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
9.5%
Weak
Equity as a share of total capital

Who owns RHJ AS?

OREMO AS
RHJ AS
NOK 11.1m rev. · NOK 552,000 profit

RHJ AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about RHJ AS

Who owns RHJ AS?

OREMO AS is the largest registered owner, with 100.0%.

What is the revenue of RHJ AS?

RHJ AS had revenue of NOK 11.1m in 2024.

Who is the general manager of RHJ AS?

Roar Henry Jakobsen is registered as general manager of RHJ AS.

Where is RHJ AS based?

RHJ AS has its business address in Degernes.

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.