BIZTRAC BETA
General medical practice activities

STERK HELSE OG TRENING NYDALEN AS

Org. no. 834391422 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Operating profit NOK −51,000
Equity NOK 14,000
Incorporated 2024
Employees 20
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−51k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

STERK HELSE OG TRENING NYDALEN AS is registered as a limited company in Oslo, Oslo with organisation number 834391422. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2024 and has 20 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen fysioterapi og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures · 2024

Operating profit
NOK −51,000
Equity
NOK 14,000
Est. value
NOK 22,000

Financial health · 2024

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

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

Who owns STERK HELSE OG TRENING NYDALEN AS?

STERK GROUP AS
STERK HELSE OG TRENING NYDALEN AS
· NOK −51,000 profit

STERK HELSE OG TRENING NYDALEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about STERK HELSE OG TRENING NYDALEN AS

Who owns STERK HELSE OG TRENING NYDALEN AS?

STERK GROUP AS is the largest registered owner, with 100.0%.

Where is STERK HELSE OG TRENING NYDALEN AS based?

STERK HELSE OG TRENING NYDALEN AS has its business address in Oslo.

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.