BIZTRAC BETA
COMPANY REGISTER PROFILE
935322049 ORG. NO. 2025 ACCOUNTS 7 SECTIONS
Active UPDATED 15.06.2026
Uoppgitt

LE CHIEM HOLDING AS

Org. no. 935322049 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Operating profit NOK −7,000
Equity NOK −7,000
Incorporated 2025
Share capital NOK 30,000

Signals

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

LE CHIEM HOLDING AS is registered as a limited company in Oslo, Oslo with organisation number 935322049. The business is classified under uoppgitt (NACE 00.000). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Investere i selskaper og eiendom og alt annet som naturlig faller sammen med dette, herunder å delta i andre selskaper med lignende virksomhet, kjøp og salg av aksjer, eller på annen måte gjøre seg interessert i andre foretagende.”.

Key figures · 2025

Operating profit
NOK −7,000
Equity
NOK −7,000

Financial health · 2025

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

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

Who owns LE CHIEM HOLDING AS?

KINGSLEY MINH NGUYEN LE
LE CHIEM HOLDING AS
· NOK −7,000 profit

LE CHIEM HOLDING AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about LE CHIEM HOLDING AS

Who owns LE CHIEM HOLDING AS?

KINGSLEY MINH NGUYEN LE is the largest registered owner, with 50.0%.

Who is the general manager of LE CHIEM HOLDING AS?

Kingsley Minh Nguyen Le is registered as general manager of LE CHIEM HOLDING AS.

Where is LE CHIEM HOLDING AS based?

LE CHIEM HOLDING 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.