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

ORKIDE RESTAURANT AS

Org. no. 999123619 Limited company (AS) Indre Østfold Incorporated 2012 Active
Ownership graph ↗
Revenue 2025 NOK 15.0m
Operating profit NOK 1.7m
Equity NOK 3.9m
Incorporated 2012
Employees 15
Share capital NOK 30,000

ORKIDE RESTAURANT AS is registered as a limited company in Indre Østfold, Østfold with organisation number 999123619. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 15 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Restaurant- og cateringvirksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 15.0m in revenue and NOK 1.7m in operating profit.

Former names: ASIA SUPERMARKED AS

Key figures · 2025

Revenue
NOK 15.0m
▲ +0 %
Operating profit
NOK 1.7m
▼ −41 %
Equity
NOK 3.9m
▼ −23 %
Est. value
NOK 9.7m

Financial health · 2025

Liquidity
2.09
Very good
Current assets ÷ current liabilities
Profitability
27.6%
Very good
Return on total assets
Solidity
66.5%
Very good
Equity as a share of total capital

Who owns ORKIDE RESTAURANT AS?

ORKIDE RESTAURANT AS
NOK 15.0m rev. · NOK 1.7m profit

ORKIDE RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about ORKIDE RESTAURANT AS

Who owns ORKIDE RESTAURANT AS?

Linh Thi My Tran is the largest registered owner, with 100.0%.

What is the revenue of ORKIDE RESTAURANT AS?

ORKIDE RESTAURANT AS had revenue of NOK 15.0m in 2025.

Who is the general manager of ORKIDE RESTAURANT AS?

Linh Thi My Tran is registered as general manager of ORKIDE RESTAURANT AS.

Where is ORKIDE RESTAURANT AS based?

ORKIDE RESTAURANT AS has its business address in Askim.

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.