BIZTRAC BETA
Traditional, complementary and alternative medicine activities

FIGENSCHOU KIROPRAKTOR AS

Org. no. 917991189 Limited company (AS) Sandnes Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 1.2m
Operating profit NOK 154,000
Equity NOK 260,000
Incorporated 2016
Share capital NOK 30,000

FIGENSCHOU KIROPRAKTOR AS is registered as a limited company in Sandnes, Rogaland with organisation number 917991189. The business is classified under traditional, complementary and alternative medicine activities (NACE 86.960). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kiropraktikk og tilbyr tjenester innen helse og trening.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.2m in revenue and NOK 154,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.2m
Operating profit
NOK 154,000
Equity
NOK 260,000
Est. value
NOK 896,000

Financial health · 2024

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

Who owns FIGENSCHOU KIROPRAKTOR AS?

RENEE NILSEN FIGENSCHOU
FIGENSCHOU KIROPRAKTOR AS
NOK 1.2m rev. · NOK 154,000 profit

FIGENSCHOU KIROPRAKTOR AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about FIGENSCHOU KIROPRAKTOR AS

Who owns FIGENSCHOU KIROPRAKTOR AS?

RENEE NILSEN FIGENSCHOU is the largest registered owner, with 100.0%.

What is the revenue of FIGENSCHOU KIROPRAKTOR AS?

FIGENSCHOU KIROPRAKTOR AS had revenue of NOK 1.2m in 2024.

Who is the general manager of FIGENSCHOU KIROPRAKTOR AS?

Renee Nilsen Figenschou is registered as general manager of FIGENSCHOU KIROPRAKTOR AS.

Where is FIGENSCHOU KIROPRAKTOR AS based?

FIGENSCHOU KIROPRAKTOR AS has its business address in Sandnes.

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.