BIZTRAC BETA
Traditional, complementary and alternative medicine activities

SINI KIROPRAKTIKK AS

Org. no. 926117920 Limited company (AS) Arendal Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 1.2m
Operating profit NOK 27,000
Equity NOK 713,000
Incorporated 2020
Share capital NOK 500,000

SINI KIROPRAKTIKK AS is registered as a limited company in Arendal, Agder with organisation number 926117920. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2020. Registered share capital is NOK 500,000, divided into 500000 shares. The company's stated purpose is: “Å drive kiropraktorvirksomhet, samt finansielle investeringer, herunder omsettelige verdipapirer, eiendom og andre realaktiva.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.2m in revenue and NOK 27,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.2m
Operating profit
NOK 27,000
Equity
NOK 713,000
Est. value
NOK 610,000

Financial health · 2025

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

Who owns SINI KIROPRAKTIKK AS?

NICOLAY CORNELIUS HØST
SINI KIROPRAKTIKK AS
NOK 1.2m rev. · NOK 27,000 profit

SINI KIROPRAKTIKK AS has 1 registered shareholder:

All shareholders and roles →

Which companies does SINI KIROPRAKTIKK AS own?

SINI KIROPRAKTIKK AS holds stakes in 2 companies:

See the full ownership structure →

Frequently asked questions about SINI KIROPRAKTIKK AS

Who owns SINI KIROPRAKTIKK AS?

NICOLAY CORNELIUS HØST is the largest registered owner, with 100.0%.

What is the revenue of SINI KIROPRAKTIKK AS?

SINI KIROPRAKTIKK AS had revenue of NOK 1.2m in 2025.

Where is SINI KIROPRAKTIKK AS based?

SINI KIROPRAKTIKK AS has its business address in Arendal.

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.