biztrac. BETA
COMPANY REGISTER PROFILE
931148230 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 03.10.2026
General medical practice activities

TORGET HELSESENTER AS

Org. no. 931148230 Limited company (AS) Drammen Incorporated 2023 Active
Revenue 2025 NOK 2.8m
Operating profit NOK −443,000
Equity NOK −244,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−244k kr).

TORGET HELSESENTER AS is registered as a limited company in Drammen, Buskerud with organisation number 931148230. The business is classified under general medical practice activities (NACE 86.210). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Driftselskap for å drive Torget legesenter som er fastlegesenter.”. The most recent filed accounts, for the 2025 financial year, show NOK 2.8m in revenue and NOK −443,000 in operating profit.

Key figures · 2025

Revenue
NOK 2.8m
▲ +0 %
Operating profit
NOK −443,000
▼ −422 %
Equity
NOK −244,000
▼ −229 %

Financial health · 2025

Liquidity
0.01
Not satisfactory
Current assets ÷ current liabilities
Profitability
-84.8%
Not satisfactory
Return on total assets
Solidity
-73.8%
Weak
Equity as a share of total capital

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

Who owns TORGET HELSESENTER AS?

TORGET HELSESENTER AS
NOK 2.8m rev. · NOK −443,000 profit

TORGET HELSESENTER AS has 3 registered shareholders:

All shareholders and roles →

Frequently asked questions about TORGET HELSESENTER AS

Who owns TORGET HELSESENTER AS?

Lema Samar Omarzae is the largest registered owner, with 25.0%.

What is the revenue of TORGET HELSESENTER AS?

TORGET HELSESENTER AS had revenue of NOK 2.8m in 2025.

Where is TORGET HELSESENTER AS based?

TORGET HELSESENTER 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 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.