BIZTRAC BETA
Physiotherapy activities

HJERTE OG IDRETTSSENTERET AS

Org. no. 924205245 Limited company (AS) Drammen Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 729,000
Operating profit NOK −304
Equity NOK 115,000
Incorporated 2019
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−304 kr).

HJERTE OG IDRETTSSENTERET AS is registered as a limited company in Drammen, Buskerud with organisation number 924205245. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Fysioterapi.”. The most recent filed accounts, for the 2024 financial year, show NOK 729,000 in revenue and NOK −304 in operating profit.

Key figures · 2024

Revenue
NOK 729,000
Operating profit
NOK −304
Equity
NOK 115,000
Est. value
NOK 662,000

Financial health · 2024

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

Who owns HJERTE OG IDRETTSSENTERET AS?

SILJE REVÅ KRISTENSEN
HJERTE OG IDRETTSSENTERET AS
NOK 729,000 rev. · NOK −304 profit

HJERTE OG IDRETTSSENTERET AS has 2 registered shareholders:

All shareholders and roles →

Which companies does HJERTE OG IDRETTSSENTERET AS own?

HJERTE OG IDRETTSSENTERET AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HJERTE OG IDRETTSSENTERET AS

Who owns HJERTE OG IDRETTSSENTERET AS?

SILJE REVÅ KRISTENSEN is the largest registered owner, with 50.0%.

What is the revenue of HJERTE OG IDRETTSSENTERET AS?

HJERTE OG IDRETTSSENTERET AS had revenue of NOK 729,000 in 2024.

Where is HJERTE OG IDRETTSSENTERET AS based?

HJERTE OG IDRETTSSENTERET AS has its business address in Drammen.

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.