BIZTRAC BETA
Restaurant activities

NEW BENARES RESTAURANT AS

Org. no. 935727235 Limited company (AS) Oslo Incorporated 2025 Active
Ownership graph ↗
Revenue 2025 NOK 4.0m
Operating profit NOK −428,000
Equity NOK −404,000
Incorporated 2025
Employees 30
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2025 Bokført egenkapital er negativ (−404k kr).
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−428k kr).

NEW BENARES RESTAURANT AS is registered as a limited company in Oslo, Oslo with organisation number 935727235. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2025 and has 30 registered employees. Registered share capital is NOK 30,000, divided into 3000 shares. The company's stated purpose is: “Å kjøpe og fortsette driften av en ordinær indisk restaurant.”. The most recent filed accounts, for the 2025 financial year, show NOK 4.0m in revenue and NOK −428,000 in operating profit.

Key figures · 2025

Revenue
NOK 4.0m
Operating profit
NOK −428,000
Equity
NOK −404,000

Financial health · 2025

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

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

Who owns NEW BENARES RESTAURANT AS?

BIKASH KANDEL
NEW BENARES RESTAURANT AS
NOK 4.0m rev. · NOK −428,000 profit

NEW BENARES RESTAURANT AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about NEW BENARES RESTAURANT AS

Who owns NEW BENARES RESTAURANT AS?

BIKASH KANDEL is the largest registered owner, with 100.0%.

What is the revenue of NEW BENARES RESTAURANT AS?

NEW BENARES RESTAURANT AS had revenue of NOK 4.0m in 2025.

Where is NEW BENARES RESTAURANT AS based?

NEW BENARES 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.