BIZTRAC BETA
Restaurant activities

MLEM MLEM AS

Org. no. 934920465 Limited company (AS) Lier Incorporated 2025 Active
Ownership graph ↗
Revenue NOK 14,000
Operating profit NOK −87,000
Equity NOK −64,000
Incorporated 2025
Share capital NOK 30,000

Signals

3 flags
  • Negativ egenkapital Bokført egenkapital er negativ (−64k kr).
  • Driftsunderskudd Siste driftsresultat er negativt (−87k kr).
  • Mangler regnskap Ingen årsregnskap er registrert for selskapet.

MLEM MLEM AS is registered as a limited company in Lier, Buskerud with organisation number 934920465. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Selge varer og tjenester innen gatekjøkkendrift og annet som naturlig sammenfaller med dette samt deltakelse i andre selskaper, investeringer og nærliggende virksomhet.”.

Key figures

Revenue
NOK 14,000
Operating profit
NOK −87,000
Equity
NOK −64,000

Financial health · 2025

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

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

Who owns MLEM MLEM AS?

RONNY KHOA TRUONG TRAN
MLEM MLEM AS
NOK 14,000 rev. · NOK −87,000 profit

MLEM MLEM AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MLEM MLEM AS

Who owns MLEM MLEM AS?

RONNY KHOA TRUONG TRAN is the largest registered owner, with 100.0%.

What is the revenue of MLEM MLEM AS?

MLEM MLEM AS had revenue of NOK 14,000.

Who is the general manager of MLEM MLEM AS?

Ronny Khoa Truong Tran is registered as general manager of MLEM MLEM AS.

Where is MLEM MLEM AS based?

MLEM MLEM AS has its business address in Gullaug.

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.