BIZTRAC BETA
Other health services

REBEL MEDICAL AS

Org. no. 931846701 Limited company (AS) Flesberg Incorporated 2023 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK 0
Equity NOK 34,000
Incorporated 2023
Share capital NOK 33,000

REBEL MEDICAL AS is registered as a limited company in Flesberg, Buskerud with organisation number 931846701. The business is classified under other health services (NACE 86.993). The company was incorporated in 2023. Registered share capital is NOK 33,000, divided into 33333 shares. The company's stated purpose is: “Privat og bedrift helsetjenester, eventproduksjon, catering, lydutleie og kursvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK 34,000
Est. value
NOK 53,000

Financial health · 2024

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

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

Who owns REBEL MEDICAL AS?

SINDRE HAGA ANDREASSEN
REBEL MEDICAL AS
NOK 0 rev. · NOK 0 profit

REBEL MEDICAL AS has 1 registered shareholder:

All shareholders and roles →

Which companies does REBEL MEDICAL AS own?

REBEL MEDICAL AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about REBEL MEDICAL AS

Who owns REBEL MEDICAL AS?

SINDRE HAGA ANDREASSEN is the largest registered owner, with 100.0%.

What is the revenue of REBEL MEDICAL AS?

REBEL MEDICAL AS had revenue of NOK 0 in 2024.

Who is the general manager of REBEL MEDICAL AS?

Sindre Haga Andreassen is registered as general manager of REBEL MEDICAL AS.

Where is REBEL MEDICAL AS based?

REBEL MEDICAL AS has its business address in Flesberg.

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.