BIZTRAC BETA
Other non-specialised retail sale

KPOPXO AS

Org. no. 931469339 Limited company (AS) Oslo Incorporated 2023 Active
Ownership graph ↗
Revenue 2025 NOK 3,000
Operating profit NOK −3,000
Equity NOK 19,000
Incorporated 2023
Share capital NOK 30,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−3k kr).

KPOPXO AS is registered as a limited company in Oslo, Oslo with organisation number 931469339. The business is classified under other non-specialised retail sale (NACE 47.120). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Tilby varer og tjenester til K-pop fandomen i Norge og Norden, herunder import, engros og detaljomsetning av musikkalbum og relaterte fan-produkter, netthandel, logistikk- og arrangementstjenester og markedsføring.”. The most recent filed accounts, for the 2025 financial year, show NOK 3,000 in revenue and NOK −3,000 in operating profit.

Key figures · 2025

Revenue
NOK 3,000
Operating profit
NOK −3,000
Equity
NOK 19,000
Est. value
NOK 10,000

Financial health · 2025

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

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

Who owns KPOPXO AS?

JI HYE PARK
KPOPXO AS
NOK 3,000 rev. · NOK −3,000 profit

KPOPXO AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KPOPXO AS

Who owns KPOPXO AS?

JI HYE PARK is the largest registered owner, with 70.0%.

What is the revenue of KPOPXO AS?

KPOPXO AS had revenue of NOK 3,000 in 2025.

Who is the general manager of KPOPXO AS?

Ji Hye Park is registered as general manager of KPOPXO AS.

Where is KPOPXO AS based?

KPOPXO AS has its business address in Oslo.

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.