BIZTRAC BETA
Manufacture of perfume and toilet preparations

OCEAN COSMETICS AS

Org. no. 917554862 Limited company (AS) Oslo Incorporated 2016 Active
Ownership graph ↗
Revenue 2025 NOK 33,000
Operating profit NOK −31,000
Equity NOK −414
Incorporated 2016
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−414 kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−31k kr).
  • Nylig endring 2026-05-06 Adresseendring registrert 2026-05-06.

OCEAN COSMETICS AS is registered as a limited company in Oslo, Oslo with organisation number 917554862. The business is classified under manufacture of perfume and toilet preparations (NACE 20.420). The company was incorporated in 2016. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Produksjon og salg av hudpleieprodukter med ingredienser fra havet.”. The most recent filed accounts, for the 2025 financial year, show NOK 33,000 in revenue and NOK −31,000 in operating profit.

Key figures · 2025

Revenue
NOK 33,000
Operating profit
NOK −31,000
Equity
NOK −414

Financial health · 2025

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

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

Who owns OCEAN COSMETICS AS?

CECILIE BJØRGE DYB
OCEAN COSMETICS AS
NOK 33,000 rev. · NOK −31,000 profit

OCEAN COSMETICS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about OCEAN COSMETICS AS

Who owns OCEAN COSMETICS AS?

CECILIE BJØRGE DYB is the largest registered owner, with 100.0%.

What is the revenue of OCEAN COSMETICS AS?

OCEAN COSMETICS AS had revenue of NOK 33,000 in 2025.

Where is OCEAN COSMETICS AS based?

OCEAN COSMETICS 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.