BIZTRAC BETA
Restaurant activities

KIM CHI VY CAFE AS

Org. no. 998476356 Limited company (AS) Ullensaker Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 3.0m
Operating profit NOK 71,000
Equity NOK −2.6m
Incorporated 2012
Employees 8
Share capital NOK 30,000

Signals

1 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−2,6 mill kr).

KIM CHI VY CAFE AS is registered as a limited company in Ullensaker, Akershus with organisation number 998476356. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 8 registered employees. Registered share capital is NOK 30,000, divided into 1000 shares. The company's stated purpose is: “Drives med restaurant og kaffeteria.”. The most recent filed accounts, for the 2024 financial year, show NOK 3.0m in revenue and NOK 71,000 in operating profit.

Key figures · 2024

Revenue
NOK 3.0m
Operating profit
NOK 71,000
Equity
NOK −2.6m
Est. value
NOK 545,000

Financial health · 2024

Liquidity
4.97
Very good
Current assets ÷ current liabilities
Profitability
Not available
Return on total assets
Solidity
-243.5%
Weak
Equity as a share of total capital

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

Who owns KIM CHI VY CAFE AS?

PHUONG CHI THI VY
KIM CHI VY CAFE AS
NOK 3.0m rev. · NOK 71,000 profit

KIM CHI VY CAFE AS has 2 registered shareholders:

All shareholders and roles →

Frequently asked questions about KIM CHI VY CAFE AS

Who owns KIM CHI VY CAFE AS?

PHUONG CHI THI VY is the largest registered owner, with 50.0%.

What is the revenue of KIM CHI VY CAFE AS?

KIM CHI VY CAFE AS had revenue of NOK 3.0m in 2024.

Who is the general manager of KIM CHI VY CAFE AS?

Thi Kim Chi Vy is registered as general manager of KIM CHI VY CAFE AS.

Where is KIM CHI VY CAFE AS based?

KIM CHI VY CAFE AS has its business address in Jessheim.

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.