BIZTRAC BETA
COMPANY REGISTER PROFILE
898810402 ORG. NO. 2024 ACCOUNTS 8 SECTIONS
Active UPDATED 15.06.2026
Restaurant activities

ISHNOOR & DISHAAN AS

Org. no. 898810402 Limited company (AS) Oslo Incorporated 2012 Active
Ownership graph ↗
Revenue 2024 NOK 0
Operating profit NOK −15,000
Equity NOK −1.9m
Incorporated 2012
Share capital NOK 30,000

Signals

2 flags
  • Negativ egenkapital 2024 Bokført egenkapital er negativ (−1,9 mill kr).
  • Driftsunderskudd 2024 Siste driftsresultat er negativt (−15k kr).

ISHNOOR & DISHAAN AS is registered as a limited company in Oslo, Oslo with organisation number 898810402. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2012. Registered share capital is NOK 30,000, divided into 300 shares. The company's stated purpose is: “Drive kafe og restaurantvirksomhet.”. The most recent filed accounts, for the 2024 financial year, show NOK 0 in revenue and NOK −15,000 in operating profit.

Key figures · 2024

Revenue
NOK 0
Operating profit
NOK −15,000
Equity
NOK −1.9m

Financial health · 2024

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

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

Who owns ISHNOOR & DISHAAN AS?

No shareholders are registered for ISHNOOR & DISHAAN AS in open Norwegian sources. Shareholder data exists mainly for limited companies (AS/ASA).

Frequently asked questions about ISHNOOR & DISHAAN AS

What is the revenue of ISHNOOR & DISHAAN AS?

ISHNOOR & DISHAAN AS had revenue of NOK 0 in 2024.

Who is the general manager of ISHNOOR & DISHAAN AS?

Jaideep Singh Khehra is registered as general manager of ISHNOOR & DISHAAN AS.

Where is ISHNOOR & DISHAAN AS based?

ISHNOOR & DISHAAN 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.