biztrac. BETA
COMPANY REGISTER PROFILE
916170440 ORG. NO. 2025 ACCOUNTS 8 SECTIONS
Active UPDATED 03.10.2026
Restaurant activities

CHAMO AS

Org. no. 916170440 Limited company (AS) Tromsø Incorporated 2015 Active
Ownership graph ↗
Revenue 2025 NOK 9.7m
Operating profit NOK −360,000
Equity NOK 21,000
Incorporated 2015
Employees 14
Share capital NOK 30,000

Signals

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

CHAMO AS is registered as a limited company in Tromsø, Troms with organisation number 916170440. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2015 and has 14 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Drive med restaurantvirksomhet og det som naturlig hører inn under dette.”. The most recent filed accounts, for the 2025 financial year, show NOK 9.7m in revenue and NOK −360,000 in operating profit.

Key figures · 2025

Revenue
NOK 9.7m
▲ +16 %
Operating profit
NOK −360,000
▼ −173 %
Equity
NOK 21,000
▼ −94 %
Est. value
NOK 39,000

Financial health · 2025

Liquidity
0.76
Weak
Current assets ÷ current liabilities
Profitability
-18.0%
Not satisfactory
Return on total assets
Solidity
1.1%
Weak
Equity as a share of total capital

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

Who owns CHAMO AS?

CHAMO AS
NOK 9.7m rev. · NOK −360,000 profit

CHAMO AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about CHAMO AS

Who owns CHAMO AS?

Sum Dick Chiang is the largest registered owner, with 100.0%.

What is the revenue of CHAMO AS?

CHAMO AS had revenue of NOK 9.7m in 2025.

Who is the general manager of CHAMO AS?

Poa Sam Chiang is registered as general manager of CHAMO AS.

Where is CHAMO AS based?

CHAMO AS has its business address in Tromsø.

Source: Biztrac.no · Data from the Brønnøysund Register Centre and the Norwegian Tax Administration · Last updated 03.10.2026.

Report a problem

Found a technical fault, or something wrong in the data? Tell us what happened.