BIZTRAC BETA
Manufacture of perfume and toilet preparations

DRYSKIN AS

Org. no. 922068364 Limited company (AS) Oslo Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 23,000
Operating profit NOK −33,000
Equity NOK −138,000
Incorporated 2018
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−138k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−33k kr).

DRYSKIN AS is registered as a limited company in Oslo, Oslo with organisation number 922068364. The business is classified under manufacture of perfume and toilet preparations (NACE 20.420). The company was incorporated in 2018. Registered share capital is NOK 30,000, divided into 200 shares. The company's stated purpose is: “Utvikle, markedsføre og selge produkter som forebygger og behandler tørr hud hos forbrukere og pasienter med eksem.”. The most recent filed accounts, for the 2025 financial year, show NOK 23,000 in revenue and NOK −33,000 in operating profit.

Key figures · 2025

Revenue
NOK 23,000
Operating profit
NOK −33,000
Equity
NOK −138,000

Financial health · 2025

Liquidity
1.61
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-1974.2%
Weak
Equity as a share of total capital

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

Who owns DRYSKIN AS?

JAN ØYVIND HOLM
DRYSKIN AS
NOK 23,000 rev. · NOK −33,000 profit

DRYSKIN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about DRYSKIN AS

Who owns DRYSKIN AS?

JAN ØYVIND HOLM is the largest registered owner, with 50.0%.

What is the revenue of DRYSKIN AS?

DRYSKIN AS had revenue of NOK 23,000 in 2025.

Who is the general manager of DRYSKIN AS?

Jan Øyvind Holm is registered as general manager of DRYSKIN AS.

Where is DRYSKIN AS based?

DRYSKIN 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.