BIZTRAC BETA
Traditional, complementary and alternative medicine activities

KIROPRAKTORHUSET AS

Org. no. 913743997 Limited company (AS) Larvik Incorporated 2014 Active
Ownership graph ↗
Revenue 2025 NOK 4.9m
Operating profit NOK 58,000
Equity NOK 276,000
Incorporated 2014
Share capital NOK 30,000

KIROPRAKTORHUSET AS is registered as a limited company in Larvik, Vestfold with organisation number 913743997. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2014. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Helsevirksomhet, kiropraktisk undersøkelse, diagnostisering og behandling av pasienter, samt salg av andre produkter og tjenester som naturlig faller sammen med dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.9m in revenue and NOK 58,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.9m
Operating profit
NOK 58,000
Equity
NOK 276,000
Est. value
NOK 436,000

Financial health · 2025

Liquidity
1.27
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
24.7%
Good
Equity as a share of total capital

Who owns KIROPRAKTORHUSET AS?

KRISTIN LO
KIROPRAKTORHUSET AS
NOK 4.9m rev. · NOK 58,000 profit

KIROPRAKTORHUSET AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIROPRAKTORHUSET AS

Who owns KIROPRAKTORHUSET AS?

KRISTIN LO is the largest registered owner, with 50.0%.

What is the revenue of KIROPRAKTORHUSET AS?

KIROPRAKTORHUSET AS had revenue of NOK 4.9m in 2025.

Who is the general manager of KIROPRAKTORHUSET AS?

Bente Marie Børresen is registered as general manager of KIROPRAKTORHUSET AS.

Where is KIROPRAKTORHUSET AS based?

KIROPRAKTORHUSET AS has its business address in Larvik.

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.