BIZTRAC BETA
Rental and operating of own or leased real estate

BAHADUR EIENDOM AS

Org. no. 991367640 Limited company (AS) Oslo Incorporated 2007 Active
Ownership graph ↗
Revenue 2024 NOK 2.1m
Operating profit NOK 755,000
Equity NOK 11.2m
Incorporated 2007
Share capital NOK 1.4m

BAHADUR EIENDOM AS is registered as a limited company in Oslo, Oslo with organisation number 991367640. The business is classified under rental and operating of own or leased real estate (NACE 68.200). The company was incorporated in 2007. Registered share capital is NOK 1.4m, divided into 140 shares. The company's stated purpose is: “Investering i andre selskaper samt forretningsutvikling og deltakelse i disse. Kjøp og salg av eiendom. Herunder utleie av fast eiendom. Investeringer i aksjer og verdipapirer og annan virksomhet forbundet med dette.”. The most recent filed accounts, for the 2024 financial year, show NOK 2.1m in revenue and NOK 755,000 in operating profit.

Key figures · 2024

Revenue
NOK 2.1m
Operating profit
NOK 755,000
Equity
NOK 11.2m
Est. value
NOK 10.0m

Financial health · 2024

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

Who owns BAHADUR EIENDOM AS?

JEHANGIR BAHADUR
BAHADUR EIENDOM AS
NOK 2.1m rev. · NOK 755,000 profit

BAHADUR EIENDOM AS has 1 registered shareholder:

All shareholders and roles →

Which companies does BAHADUR EIENDOM AS own?

BAHADUR EIENDOM AS holds a stake in 1 company:

See the full ownership structure →

Frequently asked questions about BAHADUR EIENDOM AS

Who owns BAHADUR EIENDOM AS?

JEHANGIR BAHADUR is the largest registered owner, with 100.0%.

What is the revenue of BAHADUR EIENDOM AS?

BAHADUR EIENDOM AS had revenue of NOK 2.1m in 2024.

Where is BAHADUR EIENDOM AS based?

BAHADUR EIENDOM 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.