BIZTRAC BETA
Physiotherapy activities

HOEL FYSIOTERAPI OG HELSE AS

Org. no. 930104787 Limited company (AS) Drammen Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 2.3m
Operating profit NOK 519,000
Equity NOK 1.4m
Incorporated 2022
Share capital NOK 30,000

HOEL FYSIOTERAPI OG HELSE AS is registered as a limited company in Drammen, Buskerud with organisation number 930104787. The business is classified under physiotherapy activities (NACE 86.950). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Fysioterapitjeneste, investeringer i andre selskapet og annet som hører til i denne forbindelse.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.3m in revenue and NOK 519,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.3m
Operating profit
NOK 519,000
Equity
NOK 1.4m
Est. value
NOK 2.9m

Financial health · 2025

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

Who owns HOEL FYSIOTERAPI OG HELSE AS?

MARIUS JENSEN HOEL
HOEL FYSIOTERAPI OG HELSE AS
NOK 2.3m rev. · NOK 519,000 profit

HOEL FYSIOTERAPI OG HELSE AS has 1 registered shareholder:

All shareholders and roles →

Which companies does HOEL FYSIOTERAPI OG HELSE AS own?

HOEL FYSIOTERAPI OG HELSE AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about HOEL FYSIOTERAPI OG HELSE AS

Who owns HOEL FYSIOTERAPI OG HELSE AS?

MARIUS JENSEN HOEL is the largest registered owner, with 100.0%.

What is the revenue of HOEL FYSIOTERAPI OG HELSE AS?

HOEL FYSIOTERAPI OG HELSE AS had revenue of NOK 2.3m in 2025.

Where is HOEL FYSIOTERAPI OG HELSE AS based?

HOEL FYSIOTERAPI OG HELSE 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.