BIZTRAC BETA
Traditional, complementary and alternative medicine activities

AKUTT KIROPRAKTIKK OSLO AS

Org. no. 928504026 Limited company (AS) Oslo Incorporated 2021 Active
Ownership graph ↗
Revenue 2025 NOK 5.2m
Operating profit NOK 891,000
Equity NOK 30,000
Incorporated 2021
Share capital NOK 30,000

AKUTT KIROPRAKTIKK OSLO AS is registered as a limited company in Oslo, Oslo with organisation number 928504026. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2021. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Kiropraktikk.”. The most recent filed accounts, for the 2025 financial year, show NOK 5.2m in revenue and NOK 891,000 in operating profit.

Key figures · 2025

Revenue
NOK 5.2m
Operating profit
NOK 891,000
Equity
NOK 30,000
Est. value
NOK 3.5m

Financial health · 2025

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

Solidity capped at Weak because equity is below NOK 100,000.

Who owns AKUTT KIROPRAKTIKK OSLO AS?

VIVOT HOLDING AS
AKUTT KIROPRAKTIKK OSLO AS
NOK 5.2m rev. · NOK 891,000 profit

AKUTT KIROPRAKTIKK OSLO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about AKUTT KIROPRAKTIKK OSLO AS

Who owns AKUTT KIROPRAKTIKK OSLO AS?

VIVOT HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of AKUTT KIROPRAKTIKK OSLO AS?

AKUTT KIROPRAKTIKK OSLO AS had revenue of NOK 5.2m in 2025.

Who is the general manager of AKUTT KIROPRAKTIKK OSLO AS?

Odd Frode Vivot Sørholt is registered as general manager of AKUTT KIROPRAKTIKK OSLO AS.

Where is AKUTT KIROPRAKTIKK OSLO AS based?

AKUTT KIROPRAKTIKK OSLO AS has its business address in Oslo.

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.