BIZTRAC BETA
Retail sale of footwear and leather goods

SNOS MOA AS

Org. no. 812802062 Limited company (AS) Ålesund Incorporated 2013 Active
Ownership graph ↗
Revenue 2025 NOK 4.3m
Operating profit NOK 164,000
Equity NOK 371,000
Incorporated 2013
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 MOA AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 812802062. The business is classified under retail sale of footwear and leather goods (NACE 47.720). The company was incorporated in 2013. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive handelsvirksomhet, og dermed beslektet virksomhet. Gjennom aksjetegning eller på annen måte skal selskapet kunne delta i andre foretagender.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.3m in revenue and NOK 164,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.3m
Operating profit
NOK 164,000
Equity
NOK 371,000
Est. value
NOK 826,000

Financial health · 2025

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

Who owns SNOS MOA AS?

SN OS HOLDING AS
SNOS MOA AS
NOK 4.3m rev. · NOK 164,000 profit

SNOS MOA AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about SNOS MOA AS

Who owns SNOS MOA AS?

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

What is the revenue of SNOS MOA AS?

SNOS MOA AS had revenue of NOK 4.3m in 2025.

Who is the general manager of SNOS MOA AS?

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

Where is SNOS MOA AS based?

SNOS MOA AS has its business address in Ålesund.

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.