BIZTRAC BETA
Retail sale of footwear and leather goods

SNOS STORO AS

Org. no. 929552466 Limited company (AS) Oslo Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 11.5m
Operating profit NOK 2.1m
Equity NOK 592,000
Incorporated 2022
Employees 7
Share capital NOK 30,000

Signals

1 flags
  • Ingen revisor Selskapet har ingen registrert revisor. Vanlig for små AS som har valgt bort revisjon, men verdt å merke seg.

SNOS STORO AS is registered as a limited company in Oslo, Oslo with organisation number 929552466. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2022 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 100 shares. The company's stated purpose is: “Butikkhandel med reiseeffekter, vesker og andre lærvarer, samt naturlig tilhørende virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.5m in revenue and NOK 2.1m in operating profit.

Key figures · 2025

Revenue
NOK 11.5m
Operating profit
NOK 2.1m
Equity
NOK 592,000
Est. value
NOK 6.9m

Financial health · 2025

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

Who owns SNOS STORO AS?

SN OS HOLDING AS
SNOS STORO AS
NOK 11.5m rev. · NOK 2.1m profit

SNOS STORO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNOS STORO AS

Who owns SNOS STORO AS?

SN OS HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of SNOS STORO AS?

SNOS STORO AS had revenue of NOK 11.5m in 2025.

Who is the general manager of SNOS STORO AS?

Ole Sverre Mengkrog is registered as general manager of SNOS STORO AS.

Where is SNOS STORO AS based?

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