BIZTRAC BETA
Restaurant activities

MISTER INDIA RESTAURANT AS

Org. no. 999031803 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 18.3m
Operating profit NOK 265,000
Equity NOK 15.6m
Incorporated 2012
Employees 23
Share capital NOK 30,000

MISTER INDIA RESTAURANT AS is registered as a limited company in Oslo, Oslo with organisation number 999031803. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012 and has 23 registered employees. Registered share capital is NOK 30,000, divided into 30 shares. The company's stated purpose is: “Restaurantdrift, herunder å delta i andre selskaper, samt alt hva hermed står i forbindelse.”. The most recent filed accounts, for the 2024 financial year, show NOK 18.3m in revenue and NOK 265,000 in operating profit.

Key figures · 2024

Revenue
NOK 18.3m
Operating profit
NOK 265,000
Equity
NOK 15.6m
Est. value
NOK 9.3m

Financial health · 2024

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

Who owns MISTER INDIA RESTAURANT AS?

MISTER INDIA HOLDING AS
MISTER INDIA RESTAURANT AS
NOK 18.3m rev. · NOK 265,000 profit

MISTER INDIA RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about MISTER INDIA RESTAURANT AS

Who owns MISTER INDIA RESTAURANT AS?

MISTER INDIA HOLDING AS is the largest registered owner, with 100.0%.

What is the revenue of MISTER INDIA RESTAURANT AS?

MISTER INDIA RESTAURANT AS had revenue of NOK 18.3m in 2024.

Who is the general manager of MISTER INDIA RESTAURANT AS?

Sanjiv Sharma is registered as general manager of MISTER INDIA RESTAURANT AS.

Where is MISTER INDIA RESTAURANT AS based?

MISTER INDIA RESTAURANT AS has its business address in Oslo.

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.