BIZTRAC BETA
Retail sale of clothing

WEAR4U AS

Org. no. 923594663 Limited company (AS) Oslo Incorporated 2019 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −19,000
Equity NOK −78,000
Incorporated 2019
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−78k kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−19k kr).

WEAR4U AS is registered as a limited company in Oslo, Oslo with organisation number 923594663. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2019. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Handel, nettsalg, design og merkevarebygging av klær og kleskonfeksjon, undertøy, sportsutstyr og smykker i inn og utland, samt virksomhet som står i tilknytning til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −19,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −19,000
Equity
NOK −78,000

Financial health · 2024

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

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

Who owns WEAR4U AS?

ALEXANDER ANDRÉ CHINNAPPEN
WEAR4U AS
NOK 0 rev. · NOK −19,000 profit

WEAR4U AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about WEAR4U AS

Who owns WEAR4U AS?

ALEXANDER ANDRÉ CHINNAPPEN is the largest registered owner, with 50.0%.

What is the revenue of WEAR4U AS?

WEAR4U AS had revenue of NOK 0 in 2024.

Who is the general manager of WEAR4U AS?

Rajan Chinnappen is registered as general manager of WEAR4U AS.

Where is WEAR4U AS based?

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