BIZTRAC BETA
Physiotherapy activities

STYRK FYSIOTERAPI AS

Org. no. 913061152 Limited company (AS) Levanger Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 1.1m
Operating profit NOK 147,000
Equity NOK −343,000
Incorporated 2013
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−343k kr).

STYRK FYSIOTERAPI AS is registered as a limited company in Levanger, Trøndelag with organisation number 913061152. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fysioterapi med treningssenter, samt utleie og drift av eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 1.1m in revenue and NOK 147,000 in operating profit.

Key figures · 2025

Revenue
NOK 1.1m
Operating profit
NOK 147,000
Equity
NOK −343,000
Est. value
NOK 1.1m

Financial health · 2025

Liquidity
3.58
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-3.6%
Weak
Equity as a share of total capital

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

Who owns STYRK FYSIOTERAPI AS?

DAG STEIRO
STYRK FYSIOTERAPI AS
NOK 1.1m rev. · NOK 147,000 profit

STYRK FYSIOTERAPI AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about STYRK FYSIOTERAPI AS

Who owns STYRK FYSIOTERAPI AS?

DAG STEIRO is the largest registered owner, with 50.0%.

What is the revenue of STYRK FYSIOTERAPI AS?

STYRK FYSIOTERAPI AS had revenue of NOK 1.1m in 2025.

Who is the general manager of STYRK FYSIOTERAPI AS?

Dag Steiro is registered as general manager of STYRK FYSIOTERAPI AS.

Where is STYRK FYSIOTERAPI AS based?

STYRK FYSIOTERAPI AS has its business address in Levanger.

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.