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

ROLVSØY FYSIOTERAPI AS

Org. no. 955283627 Limited company (AS) Fredrikstad Incorporated 1989 Active
Revenue 2025 NOK 633,000
Operating profit NOK 19,000
Equity NOK 98,000
Incorporated 1989
Share capital NOK 117,000

ROLVSØY FYSIOTERAPI AS is registered as a limited company in Fredrikstad, Østfold with organisation number 955283627. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 1989. Registered share capital is NOK 117,000, divided into 117 shares. The company's stated purpose is: “Drift av fysikalsk institutt. Selskapet kan delta i andre firmaer og selskaper.”. The most recent filed accounts, for the 2025 financial year, show NOK 633,000 in revenue and NOK 19,000 in operating profit.

Key figures · 2025

Revenue
NOK 633,000
▲ +19 %
Operating profit
NOK 19,000
▲ +129 %
Equity
NOK 98,000
▲ +20 %
Est. value
NOK 209,000

Financial health · 2025

Liquidity
2.82
Very good
Current assets ÷ current liabilities
Profitability
14.6%
Good
Return on total assets
Solidity
72.1%
Weak
Equity as a share of total capital

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

Who owns ROLVSØY FYSIOTERAPI AS?

ROLVSØY FYSIOTERAPI AS has 4 registered shareholders:

All shareholders and roles →

Frequently asked questions about ROLVSØY FYSIOTERAPI AS

Who owns ROLVSØY FYSIOTERAPI AS?

Marit Elisabeth Hatling Forsberg is the largest registered owner, with 33.3%.

What is the revenue of ROLVSØY FYSIOTERAPI AS?

ROLVSØY FYSIOTERAPI AS had revenue of NOK 633,000 in 2025.

Who is the general manager of ROLVSØY FYSIOTERAPI AS?

Hilde Anita Jenssen is registered as general manager of ROLVSØY FYSIOTERAPI AS.

Where is ROLVSØY FYSIOTERAPI AS based?

ROLVSØY FYSIOTERAPI AS has its business address in Rolvsøy.

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.