biztrac. BETA
COMPANY REGISTER PROFILE
918111263 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
Physiotherapy activities

STOKKA FYSIOTERAPI OG MENSENDIECK DA

Org. no. 918111263 General partnership with shared liability (DA) Stavanger Incorporated 2016 Active
Revenue 2025 NOK 675,000
Operating profit NOK 137
Equity NOK 405
Incorporated 2016

STOKKA FYSIOTERAPI OG MENSENDIECK DA is registered as a general partnership with shared liability in Stavanger, Rogaland with organisation number 918111263. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2016. The company's stated purpose is: “Drift av fellesfunksjoner i gruppepraksis i fysioterapi og virksomhet som står i forbindelse med dette. Fysioterapivirksomheten drives av den enkelte deltaker for dennes regning og risiko.”. The most recent filed accounts, for the 2025 financial year, show NOK 675,000 in revenue and NOK 137 in operating profit.

Key figures · 2025

Revenue
NOK 675,000
▲ +6 %
Operating profit
NOK 137
▲ +102 %
Equity
NOK 405
▲ +51 %
Est. value
NOK 1,000

Financial health · 2025

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

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

Who owns STOKKA FYSIOTERAPI OG MENSENDIECK DA?

No shareholders are registered for STOKKA FYSIOTERAPI OG MENSENDIECK DA in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about STOKKA FYSIOTERAPI OG MENSENDIECK DA

What is the revenue of STOKKA FYSIOTERAPI OG MENSENDIECK DA?

STOKKA FYSIOTERAPI OG MENSENDIECK DA had revenue of NOK 675,000 in 2025.

Where is STOKKA FYSIOTERAPI OG MENSENDIECK DA based?

STOKKA FYSIOTERAPI OG MENSENDIECK DA has its business address in Stavanger.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.