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

TAJMAHAL AS

Org. no. 994382292 Limited company (AS) Ålesund Incorporated 2009 Active
Revenue 2025 NOK 6.6m
Operating profit NOK −37,000
Equity NOK 836,000
Incorporated 2009
Employees 8
Share capital NOK 50,000

Signals

1 flags
  • Driftsunderskudd 2025 Siste driftsresultat er negativt (−37k kr).

TAJMAHAL AS is registered as a limited company in Ålesund, Møre og Romsdal with organisation number 994382292. The business is classified under restaurant activities (NACE 56.110). The company was incorporated in 2009 and has 8 registered employees. Registered share capital is NOK 50,000, divided into 100 shares. The company's stated purpose is: “Drive resturant med servering og hva hermed står i forbindelse, herunder delta i annen virksomhet.”. The most recent filed accounts, for the 2025 financial year, show NOK 6.6m in revenue and NOK −37,000 in operating profit.

Key figures · 2025

Revenue
NOK 6.6m
▼ −24 %
Operating profit
NOK −37,000
▼ −104 %
Equity
NOK 836,000
▼ −3 %
Est. value
NOK 1.7m

Financial health · 2025

Liquidity
1.93
Good
Current assets ÷ current liabilities
Profitability
-1.0%
Not satisfactory
Return on total assets
Solidity
48.9%
Very good
Equity as a share of total capital

Who owns TAJMAHAL AS?

TAJMAHAL AS
NOK 6.6m rev. · NOK −37,000 profit

TAJMAHAL AS has 1 registered shareholder:

All shareholders and roles →

Frequently asked questions about TAJMAHAL AS

Who owns TAJMAHAL AS?

Fahim Jan Salarzai is the largest registered owner, with 100.0%.

What is the revenue of TAJMAHAL AS?

TAJMAHAL AS had revenue of NOK 6.6m in 2025.

Who is the general manager of TAJMAHAL AS?

Fahim Jan Salarzai is registered as general manager of TAJMAHAL AS.

Where is TAJMAHAL AS based?

TAJMAHAL AS has its business address in Ålesund.

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.