BIZTRAC BETA
Other health services

OSLO HUD OG LASERKLINIKK AS

Org. no. 917576637 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 272,000
Operating profit NOK −139,000
Equity NOK 5,000
Incorporated 2016
Share capital NOK 30,000

Signals

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

OSLO HUD OG LASERKLINIKK AS is registered as a limited company in Oslo, Oslo with organisation number 917576637. The business is classified under other health services (NACE 86.993). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Medisinsk legevirksomhet og kosmetisk behandling samt det som naturlig står i forbindelse med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 272,000 in revenue and NOK −139,000 in operating profit.

Key figures · 2024

Revenue
NOK 272,000
Operating profit
NOK −139,000
Equity
NOK 5,000
Est. value
NOK 201,000

Financial health · 2024

Liquidity
0.03
Not satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
3.2%
Weak
Equity as a share of total capital

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

Who owns OSLO HUD OG LASERKLINIKK AS?

TORSTEIN GRØNSETH
OSLO HUD OG LASERKLINIKK AS
NOK 272,000 rev. · NOK −139,000 profit

OSLO HUD OG LASERKLINIKK AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OSLO HUD OG LASERKLINIKK AS

Who owns OSLO HUD OG LASERKLINIKK AS?

TORSTEIN GRØNSETH is the largest registered owner, with 50.0%.

What is the revenue of OSLO HUD OG LASERKLINIKK AS?

OSLO HUD OG LASERKLINIKK AS had revenue of NOK 272,000 in 2024.

Where is OSLO HUD OG LASERKLINIKK AS based?

OSLO HUD OG LASERKLINIKK 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.