biztrac. BETA
COMPANY REGISTER PROFILE
921374704 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Other health services

OPTIMAL HUD AS

Org. no. 921374704 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 0
Operating profit NOK 0
Equity NOK −129,000
Incorporated 2018
Share capital NOK 30,000

Signals

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

OPTIMAL HUD AS is registered as a limited company in Oslo, Oslo with organisation number 921374704. The business is classified under other health services (NACE 86.993). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Kosmetisk dermatologisk hudpleie. Drifte hudpleiesalonger og hudklinikker. Salg av produkter og behandlinger.”. The most recent filed accounts, for the 2025 financial year, show NOK 0 in revenue and NOK 0 in operating profit.

Key figures · 2025

Revenue
NOK 0
Operating profit
NOK 0
Equity
NOK −129,000
▲ +0 %

Financial health · 2025

Liquidity
0.00
Not satisfactory
Current assets ÷ current liabilities
Profitability
–
Not available
Return on total assets
Solidity
-211131.1%
Weak
Equity as a share of total capital

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

Who owns OPTIMAL HUD AS?

OPTIMAL HUD AS
NOK 0 rev. · NOK 0 profit

OPTIMAL HUD AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about OPTIMAL HUD AS

Who owns OPTIMAL HUD AS?

May Lisbeth Torheim is the largest registered owner, with 50.0%.

What is the revenue of OPTIMAL HUD AS?

OPTIMAL HUD AS had revenue of NOK 0 in 2025.

Who is the general manager of OPTIMAL HUD AS?

May Lisbeth Torheim is registered as general manager of OPTIMAL HUD AS.

Where is OPTIMAL HUD AS based?

OPTIMAL HUD 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 03.10.2026.

Report a problem

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