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

STEND HELSE AS

Org. no. 926405047 Limited company (AS) Bergen Incorporated 2020 Active
Ownership graph ↗
Revenue 2025 NOK 850,000
Operating profit NOK 168,000
Equity NOK 48,000
Incorporated 2020
Share capital NOK 30,000

STEND HELSE AS is registered as a limited company in Bergen, Vestland with organisation number 926405047. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Fysioterapibehandling og undersøkelse. Trening. Helse.”. The most recent filed accounts, for the 2025 financial year, show NOK 850,000 in revenue and NOK 168,000 in operating profit.

Former names: STEND FYSIOTERAPI AS

Key figures · 2025

Revenue
NOK 850,000
▲ +34 %
Operating profit
NOK 168,000
▲ +442 %
Equity
NOK 48,000
▲ +157 %
Est. value
NOK 484,000

Financial health · 2025

Liquidity
0.45
Not satisfactory
Current assets ÷ current liabilities
Profitability
66.2%
Very good
Return on total assets
Solidity
17.0%
Weak
Equity as a share of total capital

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

Who owns STEND HELSE AS?

STEND HELSE AS
NOK 850,000 rev. · NOK 168,000 profit

STEND HELSE AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STEND HELSE AS

Who owns STEND HELSE AS?

Martine Baartvedt Solberg is the largest registered owner, with 100.0%.

What is the revenue of STEND HELSE AS?

STEND HELSE AS had revenue of NOK 850,000 in 2025.

Who is the general manager of STEND HELSE AS?

Martine Baartvedt Solberg is registered as general manager of STEND HELSE AS.

Where is STEND HELSE AS based?

STEND HELSE AS has its business address in Fana.

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.