BIZTRAC BETA
Restaurant activities

MR. UY AS

Org. no. 917465711 Limited company (AS) Gjøvik Incorporated 2016 Active
Ownership graph ↗
Revenue 2024 NOK 4.4m
Operating profit NOK −77,000
Equity NOK −685,000
Incorporated 2016
Employees 12
Share capital NOK 530,000

Signals

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

MR. UY AS is registered as a limited company in Gjøvik, Innlandet with organisation number 917465711. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2016 and has 12 registered employees. Registered share capital is NOK 530,000, divided into 530000 shares. The company's stated purpose is: “Selskapets formål er å drive virksomhet innen restaurantdrift og servering. Selskapet kan eie fast eiendom.”. The most recent filed accounts, for the 2024 financial year, show NOK 4.4m in revenue and NOK −77,000 in operating profit.

Key figures · 2024

Revenue
NOK 4.4m
Operating profit
NOK −77,000
Equity
NOK −685,000

Financial health · 2024

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

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

Who owns MR. UY AS?

AN THOI PHAN
MR. UY AS
NOK 4.4m rev. · NOK −77,000 profit

MR. UY AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about MR. UY AS

Who owns MR. UY AS?

AN THOI PHAN is the largest registered owner, with 50.0%.

What is the revenue of MR. UY AS?

MR. UY AS had revenue of NOK 4.4m in 2024.

Who is the general manager of MR. UY AS?

Thu Minh Thi Huynh is registered as general manager of MR. UY AS.

Where is MR. UY AS based?

MR. UY 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.