BIZTRAC BETA
Event catering activities

ASIATISK NETTBUTIKK AS

Org. no. 926080717 Limited company (AS) Harstad Incorporated 2020 Active
Ownership graph ↗
Revenue 2024 NOK 181,000
Operating profit NOK −13,000
Equity NOK 1.6m
Incorporated 2020
Share capital NOK 30,000

Signals

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

ASIATISK NETTBUTIKK AS is registered as a limited company in Harstad, Troms with organisation number 926080717. The business is classified under event catering activities (NACE 56.210). The company was incorporated in 2020. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Drive med butikksalg og cateringvirksomhet, kjøp og salg av mat og rekvisita som hører inn under dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 181,000 in revenue and NOK −13,000 in operating profit.

Key figures · 2024

Revenue
NOK 181,000
Operating profit
NOK −13,000
Equity
NOK 1.6m
Est. value
NOK 899,000

Financial health · 2024

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

Who owns ASIATISK NETTBUTIKK AS?

MINH-SON TRAN
ASIATISK NETTBUTIKK AS
NOK 181,000 rev. · NOK −13,000 profit

ASIATISK NETTBUTIKK AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ASIATISK NETTBUTIKK AS

Who owns ASIATISK NETTBUTIKK AS?

MINH-SON TRAN is the largest registered owner, with 100.0%.

What is the revenue of ASIATISK NETTBUTIKK AS?

ASIATISK NETTBUTIKK AS had revenue of NOK 181,000 in 2024.

Who is the general manager of ASIATISK NETTBUTIKK AS?

Ngan Thanh Thi Ngo is registered as general manager of ASIATISK NETTBUTIKK AS.

Where is ASIATISK NETTBUTIKK AS based?

ASIATISK NETTBUTIKK AS has its business address in Harstad.

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.