BIZTRAC BETA
Restaurant activities

ZLZ AS

Org. no. 921505531 Limited company (AS) Lillestrøm Incorporated 2018 Active
Ownership graph ↗
Revenue 2025 NOK 11.6m
Operating profit NOK −391,000
Equity NOK 2.3m
Incorporated 2018
Employees 10
Share capital NOK 100,000

Signals

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

ZLZ AS is registered as a limited company in Lillestrøm, Akershus with organisation number 921505531. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2018 and has 10 registered employees. Registered share capital is NOK 100,000, divided into 100 shares. The company's stated purpose is: “Cafe og restaurantvirksomhet og andre produkter/tjenester som naturlig hører til dette, herunder å delta i andre selskap med lignende virksomhet, og kjøp og salg av aksjer eller på annen måte gjøre seg interessert i andre foretak. Selskapet kan også drive med kjøp/drift av fast eiendom.”. The most recent filed accounts, for the 2025 financial year, show NOK 11.6m in revenue and NOK −391,000 in operating profit.

Key figures · 2025

Revenue
NOK 11.6m
Operating profit
NOK −391,000
Equity
NOK 2.3m
Est. value
NOK 9.3m

Financial health · 2025

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

Who owns ZLZ AS?

LI ZHU
ZLZ AS
NOK 11.6m rev. · NOK −391,000 profit

ZLZ AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about ZLZ AS

Who owns ZLZ AS?

LI ZHU is the largest registered owner, with 66.0%.

What is the revenue of ZLZ AS?

ZLZ AS had revenue of NOK 11.6m in 2025.

Who is the general manager of ZLZ AS?

Li Zhu is registered as general manager of ZLZ AS.

Where is ZLZ AS based?

ZLZ AS has its business address in Lillestrøm.

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.