BIZTRAC BETA
Mobile food service activities

LUCKY PANDA AS

Org. no. 929216881 Limited company (AS) Sørreisa Incorporated 2022 Active
Ownership graph ↗
Revenue 2025 NOK 461,000
Operating profit NOK −42,000
Equity NOK −11,000
Incorporated 2022
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−11k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−42k kr).

LUCKY PANDA AS is registered as a limited company in Sørreisa, Troms with organisation number 929216881. The business is classified under mobile food service activities (NACE 56.120). The company was incorporated in 2022. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Salg av mat og kioskvarer fra mobil salgsvogn. Import og salg av gaveartikler, kunst, elektronikk og klær fra Kina. Tolketjenester og konsulentvirksomhet for firmaer som driver eksport/import til/fra Kina. Turistguiding.”. The most recent filed accounts, for the 2025 financial year, show NOK 461,000 in revenue and NOK −42,000 in operating profit.

Key figures · 2025

Revenue
NOK 461,000
Operating profit
NOK −42,000
Equity
NOK −11,000

Financial health · 2025

Liquidity
0.82
Weak
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-21.8%
Weak
Equity as a share of total capital

Solidity capped at Weak because equity is below NOK 100,000.

Who owns LUCKY PANDA AS?

JIE BAI
LUCKY PANDA AS
NOK 461,000 rev. · NOK −42,000 profit

LUCKY PANDA AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LUCKY PANDA AS

Who owns LUCKY PANDA AS?

JIE BAI is the largest registered owner, with 50.0%.

What is the revenue of LUCKY PANDA AS?

LUCKY PANDA AS had revenue of NOK 461,000 in 2025.

Where is LUCKY PANDA AS based?

LUCKY PANDA AS has its business address in Sørreisa.

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.