BIZTRAC BETA
Non-specialised retail sale of predominately food, beverages or tobacco

ÅLESUND ASIA SHOP AS

Org. no. 999176534 Limited company (AS) Ålesund Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 9.1m
Operating profit NOK 141,000
Equity NOK 348,000
Incorporated 2012
Employees 7
Share capital NOK 30,000

ÅLESUND ASIA SHOP AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 999176534. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2012 and has 7 registered employees. Registered share capital is NOK 30,000, divided into 60 shares. The company's stated purpose is: “Salg av kolonialvarer og det som naturlig hører til dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 9.1m in revenue and NOK 141,000 in operating profit.

Key figures · 2024

Revenue
NOK 9.1m
Operating profit
NOK 141,000
Equity
NOK 348,000
Est. value
NOK 682,000

Financial health · 2024

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

Who owns ÅLESUND ASIA SHOP AS?

AMER HUSEIN ABDULLAH
ÅLESUND ASIA SHOP AS
NOK 9.1m rev. · NOK 141,000 profit

ÅLESUND ASIA SHOP AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ÅLESUND ASIA SHOP AS

Who owns ÅLESUND ASIA SHOP AS?

AMER HUSEIN ABDULLAH is the largest registered owner, with 100.0%.

What is the revenue of ÅLESUND ASIA SHOP AS?

ÅLESUND ASIA SHOP AS had revenue of NOK 9.1m in 2024.

Who is the general manager of ÅLESUND ASIA SHOP AS?

Amer Husein Abdullah is registered as general manager of ÅLESUND ASIA SHOP AS.

Where is ÅLESUND ASIA SHOP AS based?

ÅLESUND ASIA SHOP 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.