BIZTRAC BETA
Activities of specialist physicians, other than psychiatrists

SKJØNNHETSLEGEN AS

Org. no. 922332126 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 3.2m
Operating profit NOK −260,000
Equity NOK 972,000
Incorporated 2019
Share capital NOK 30,000

Signals

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

SKJØNNHETSLEGEN AS is registered as a limited company in Oslo, Oslo with organisation number 922332126. The business is classified under activities of specialist physicians, other than psychiatrists (NACE 86.221). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Tilby kosmetiske og medisinske behandlinger utført av lege. Det går under allmenn legetjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.2m in revenue and NOK −260,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.2m
Operating profit
NOK −260,000
Equity
NOK 972,000
Est. value
NOK 3.0m

Financial health · 2024

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

Who owns SKJØNNHETSLEGEN AS?

TOSEEF ARSHAD
SKJØNNHETSLEGEN AS
NOK 3.2m rev. · NOK −260,000 profit

SKJØNNHETSLEGEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about SKJØNNHETSLEGEN AS

Who owns SKJØNNHETSLEGEN AS?

TOSEEF ARSHAD is the largest registered owner, with 50.0%.

What is the revenue of SKJØNNHETSLEGEN AS?

SKJØNNHETSLEGEN AS had revenue of NOK 3.2m in 2024.

Who is the general manager of SKJØNNHETSLEGEN AS?

Mohammed Usman Akram is registered as general manager of SKJØNNHETSLEGEN AS.

Where is SKJØNNHETSLEGEN AS based?

SKJØNNHETSLEGEN AS has its business address in Oslo.

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.