biztrac. BETA
COMPANY REGISTER PROFILE
932737949 ORG. NO. 2023 ACCOUNTS 9 SECTIONS
Compulsory dissolution UPDATED 03.10.2026
⚠DELIGHT TANDOORI AS is registered as “Compulsory dissolution” with the Brønnøysund Register Centre.
Restaurant activities

DELIGHT TANDOORI AS

Org. no. 932737949 Limited company (AS) Gjøvik Incorporated 2023 Compulsory dissolution
Ownership graph ↗
Operating profit NOK 0
Equity NOK 30,000
Incorporated 2023
Share capital NOK 30,000

Signals

2 flags
  • Tvangsoppløsning Selskapet er under tvangsoppløsning.
  • Utdatert regnskap Siste registrerte regnskap er fra 2023.

DELIGHT TANDOORI AS is registered as a limited company in Gjøvik, Innlandet with organisation number 932737949. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2023. Registered share capital is NOK 30,000, divided into 30000 shares. The company's stated purpose is: “Drift av restauranter og kafeer.”.

Key figures · 2023

Operating profit
NOK 0
Equity
NOK 30,000

Financial health · 2023

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

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

Who owns DELIGHT TANDOORI AS?

DELIGHT TANDOORI AS has 3 registered shareholders:

The company is not in the Tax Administration's shareholder register for 2025. The list shows the owners at the end of 2024.

All shareholders and roles →

Frequently asked questions about DELIGHT TANDOORI AS

Who owns DELIGHT TANDOORI AS?

Moqadas Haider Syed is the largest registered owner, with 45.0%.

Who is the general manager of DELIGHT TANDOORI AS?

Moqadas Haider Syed is registered as general manager of DELIGHT TANDOORI AS.

Where is DELIGHT TANDOORI AS based?

DELIGHT TANDOORI AS has its business address in Gjøvik.

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.