BIZTRAC BETA
Retail sale of clothing

COMPANYS STORO AS

Org. no. 933725871 Limited company (AS) Oslo Incorporated 2024 Active
Ownership graph ↗
Revenue 2024 NOK 3.1m
Operating profit NOK −372,000
Equity NOK 2.0m
Incorporated 2024
Employees 9
Share capital NOK 30,000

Signals

2 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−372k kr).
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

COMPANYS STORO AS is registered as a limited company in Oslo, Oslo with organisation number 933725871. The business is classified under retail sale of clothing (NACE 47.710). The company was incorporated in 2024 and has 9 registered employees. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drive detaljhandel med klær, inkludert, men ikke begrenset til, salg av herre-, dame- og barneklær, sko og tilbehør, samt relaterte tjenester.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.1m in revenue and NOK −372,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.1m
Operating profit
NOK −372,000
Equity
NOK 2.0m
Est. value
NOK 2.0m

Financial health · 2024

Liquidity
1.00
Satisfactory
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
28.4%
Good
Equity as a share of total capital

Who owns COMPANYS STORO AS?

COMPANYS ALOHA AS
COMPANYS STORO AS
NOK 3.1m rev. · NOK −372,000 profit

COMPANYS STORO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about COMPANYS STORO AS

Who owns COMPANYS STORO AS?

COMPANYS ALOHA AS is the largest registered owner, with 100.0%.

What is the revenue of COMPANYS STORO AS?

COMPANYS STORO AS had revenue of NOK 3.1m in 2024.

Where is COMPANYS STORO AS based?

COMPANYS STORO 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.