BIZTRAC BETA
Traditional, complementary and alternative medicine activities

HELSEHUSET KIROPRAKTIKK AS

Org. no. 915793002 Limited company (AS) Haugesund Incorporated 2015 Active
Ownership graph ↗
Revenue 2024 NOK 2.0m
Operating profit NOK 19,000
Equity NOK 157,000
Incorporated 2015
Share capital NOK 30,000

HELSEHUSET KIROPRAKTIKK AS is registered as a limited company in Haugesund, Rogaland with organisation number 915793002. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2015. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Utøvelse av kiropraktikk/andre helsetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.0m in revenue and NOK 19,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.0m
Operating profit
NOK 19,000
Equity
NOK 157,000
Est. value
NOK 188,000

Financial health · 2024

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

Who owns HELSEHUSET KIROPRAKTIKK AS?

JHR INVEST AS
HELSEHUSET KIROPRAKTIKK AS
NOK 2.0m rev. · NOK 19,000 profit

HELSEHUSET KIROPRAKTIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELSEHUSET KIROPRAKTIKK AS

Who owns HELSEHUSET KIROPRAKTIKK AS?

JHR INVEST AS is the largest registered owner, with 100.0%.

What is the revenue of HELSEHUSET KIROPRAKTIKK AS?

HELSEHUSET KIROPRAKTIKK AS had revenue of NOK 2.0m in 2024.

Who is the general manager of HELSEHUSET KIROPRAKTIKK AS?

James Henri Rijkuiter is registered as general manager of HELSEHUSET KIROPRAKTIKK AS.

Where is HELSEHUSET KIROPRAKTIKK AS based?

HELSEHUSET KIROPRAKTIKK AS has its business address in Haugesund.

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.