biztrac. BETA
COMPANY REGISTER PROFILE
932904535 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Intermediation service activities for specialised retail sale

WELLNESS AS

Org. no. 932904535 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Operating profit NOK −15,000
Equity NOK −18,000
Incorporated 2023
Share capital NOK 30,000

Signals

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

WELLNESS AS is registered as a limited company in Oslo, Oslo with organisation number 932904535. The business is classified under intermediation service activities for specialised retail sale (NACE 47.920). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “En nett-handelsplattform som tilbyr et bredt utvalg av elektronikk og klær for videre salg, samt tilbyr online tjenester til kundene. Selge konsulent tjenester, investere i aksjer, verdipapirer og delta i andre selskaper.”.

Key figures · 2025

Operating profit
NOK −15,000
▲ +54 %
Equity
NOK −18,000
▼ −484 %

Financial health · 2025

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

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

Who owns WELLNESS AS?

WELLNESS AS
· NOK −15,000 profit

WELLNESS AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about WELLNESS AS

Who owns WELLNESS AS?

Abdighani Adan is the largest registered owner, with 100.0%.

Who is the general manager of WELLNESS AS?

Abdighani Adan is registered as general manager of WELLNESS AS.

Where is WELLNESS AS based?

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