BIZTRAC BETA
Rental and operating of own or leased real estate

POON & CHEUNG AS

Org. no. 992752246 Limited company (AS) Gjøvik Incorporated 2008 Active
Ownership graph ↗
Revenue 2024 NOK 360,000
Operating profit NOK −6,000
Equity NOK 1.9m
Incorporated 2008
Share capital NOK 100,000

Signals

1 flags
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−6k kr).

POON & CHEUNG AS is registered as a limited company in Gjøvik, Innlandet with organisation number 992752246. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2008. Registered share capital is NOK 100,000, divided into 100000 shares. The company's stated purpose is: “Omsetning og utleie av fast eiendom samt alt som står i forbindelse med dette, herunder å delta i andre selskaper med lignende virksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 360,000 in revenue and NOK −6,000 in operating profit.

Key figures · 2024

Revenue
NOK 360,000
Operating profit
NOK −6,000
Equity
NOK 1.9m
Est. value
NOK 1.9m

Financial health · 2024

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

Who owns POON & CHEUNG AS?

YIU HUNG POON
POON & CHEUNG AS
NOK 360,000 rev. · NOK −6,000 profit

POON & CHEUNG AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about POON & CHEUNG AS

Who owns POON & CHEUNG AS?

YIU HUNG POON is the largest registered owner, with 100.0%.

What is the revenue of POON & CHEUNG AS?

POON & CHEUNG AS had revenue of NOK 360,000 in 2024.

Who is the general manager of POON & CHEUNG AS?

Kawai Poon is registered as general manager of POON & CHEUNG AS.

Where is POON & CHEUNG AS based?

POON & CHEUNG AS has its business address in Gjøvik.

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.