BIZTRAC BETA
Physiotherapy activities

JS FYSIOTERAPI AS

Org. no. 925591580 Limited company (AS) Narvik Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 1.7m
Operating profit NOK 174,000
Equity NOK 602,000
Incorporated 2020
Share capital NOK 50,000

JS FYSIOTERAPI AS is registered as a limited company in Narvik, Nordland with organisation number 925591580. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2020. Registered share capital is NOK 50,000, divided into 50 shares. The company's stated purpose is: “Selskapets virksomhet er å drive fysioterapi virksomhet. Selskapet kan delta i annen økonomisk virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 1.7m in revenue and NOK 174,000 in operating profit.

Key figures · 2024

Revenue
NOK 1.7m
Operating profit
NOK 174,000
Equity
NOK 602,000
Est. value
NOK 1.3m

Financial health · 2024

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

Who owns JS FYSIOTERAPI AS?

JONAS BERTHEUSSEN STRØMSNES
JS FYSIOTERAPI AS
NOK 1.7m rev. · NOK 174,000 profit

JS FYSIOTERAPI AS has 1 registered shareholder:

All shareholders and roles →

Which companies does JS FYSIOTERAPI AS own?

JS FYSIOTERAPI AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about JS FYSIOTERAPI AS

Who owns JS FYSIOTERAPI AS?

JONAS BERTHEUSSEN STRØMSNES is the largest registered owner, with 100.0%.

What is the revenue of JS FYSIOTERAPI AS?

JS FYSIOTERAPI AS had revenue of NOK 1.7m in 2024.

Who is the general manager of JS FYSIOTERAPI AS?

Jonas Bertheussen Strømsnes is registered as general manager of JS FYSIOTERAPI AS.

Where is JS FYSIOTERAPI AS based?

JS FYSIOTERAPI AS has its business address in Narvik.

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.