BIZTRAC BETA
Traditional, complementary and alternative medicine activities

VINJE KIROPRAKTOR AS

Org. no. 928978680 Limited company (AS) Averøy Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 198,000
Equity NOK 186,000
Incorporated 2022
Share capital NOK 30,000

VINJE KIROPRAKTOR AS is registered as a limited company in Averøy, Møre og Romsdal with organisation number 928978680. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Skape optimal muskel- og skjeletthelse ved kiropraktorbehandling, pilatestrening og foredrag i tverrfaglig miljø.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 198,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 198,000
Equity
NOK 186,000
Est. value
NOK 888,000

Financial health · 2025

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

Who owns VINJE KIROPRAKTOR AS?

CAMILLA JACOBSEN VINJE
VINJE KIROPRAKTOR AS
NOK 1.1m rev. · NOK 198,000 profit

VINJE KIROPRAKTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about VINJE KIROPRAKTOR AS

Who owns VINJE KIROPRAKTOR AS?

CAMILLA JACOBSEN VINJE is the largest registered owner, with 100.0%.

What is the revenue of VINJE KIROPRAKTOR AS?

VINJE KIROPRAKTOR AS had revenue of NOK 1.1m in 2025.

Who is the general manager of VINJE KIROPRAKTOR AS?

Camilla Jacobsen Vinje is registered as general manager of VINJE KIROPRAKTOR AS.

Where is VINJE KIROPRAKTOR AS based?

VINJE KIROPRAKTOR AS has its business address in Averøy.

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.