BIZTRAC BETA
Preventive health care activities

HELSECOACHEN AS

Org. no. 925199869 Limited company (AS) Bærum Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 505
Operating profit NOK −14,000
Equity NOK −32,000
Incorporated 2020
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−32k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−14k kr).

HELSECOACHEN AS is registered as a limited company in Bærum, Akershus with organisation number 925199869. The business is classified under preventive health care activities (NACE 86.992). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 10 shares. The company's stated purpose is: “Coaching innenfor helse og velvære, herunder formidling og salg av kvalitetsprodukter for positiv endring, samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 505 in revenue and NOK −14,000 in operating profit.

Key figures · 2024

Revenue
NOK 505
Operating profit
NOK −14,000
Equity
NOK −32,000

Financial health · 2024

Liquidity
0.31
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-225.7%
Weak
Equity as a share of total capital

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

Who owns HELSECOACHEN AS?

TORILL STRØM
HELSECOACHEN AS
NOK 505 rev. · NOK −14,000 profit

HELSECOACHEN AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about HELSECOACHEN AS

Who owns HELSECOACHEN AS?

TORILL STRØM is the largest registered owner, with 100.0%.

What is the revenue of HELSECOACHEN AS?

HELSECOACHEN AS had revenue of NOK 505 in 2024.

Where is HELSECOACHEN AS based?

HELSECOACHEN AS has its business address in Lysaker.

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.