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

ASIABUTIKKEN AS

Org. no. 996904725 Limited company (AS) Kristiansand Incorporated 2011 Active
Ownership graph ↗
Revenue 2024 NOK 2.7m
Operating profit NOK −56,000
Equity NOK 300,000
Incorporated 2011
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−56k kr).

ASIABUTIKKEN AS is registered as a limited company in Kristiansand, Agder with organisation number 996904725. The business is classified under non-specialised retail sale of predominately food, beverages or tobacco (NACE 47.110). The company was incorporated in 2011. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Drift av matvarebutikk. Selskapet kan også investere i selskapsandeler, fond og andre finansielle eiendeler.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.7m in revenue and NOK −56,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.7m
Operating profit
NOK −56,000
Equity
NOK 300,000
Est. value
NOK 1.0m

Financial health · 2024

Liquidity
1.89
Good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
47.2%
Very good
Equity as a share of total capital

Who owns ASIABUTIKKEN AS?

HUYNH VU
ASIABUTIKKEN AS
NOK 2.7m rev. · NOK −56,000 profit

ASIABUTIKKEN AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ASIABUTIKKEN AS

Who owns ASIABUTIKKEN AS?

HUYNH VU is the largest registered owner, with 50.0%.

What is the revenue of ASIABUTIKKEN AS?

ASIABUTIKKEN AS had revenue of NOK 2.7m in 2024.

Who is the general manager of ASIABUTIKKEN AS?

Chau Nguyen is registered as general manager of ASIABUTIKKEN AS.

Where is ASIABUTIKKEN AS based?

ASIABUTIKKEN AS has its business address in Kristiansand S.

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.