Navkar Share & Stock Brokers Private Limited.
Navkar Share & Stock Brokers Private Limited
NiveshCheck records this entry against SEBI registration number INZ000200531. The record was reviewed on 21 August 2026; confirm the current details directly with SEBI.
Registration Details
- SEBI Registration No.
- INZ000200531
- Record reviewed
- 21 August 2026
- Official source
- SEBI registered stock-broker directory
Recorded address
- Address in the source record
- 801, Dalal Street Commercial Co. operative Society Ltd 8th floor, GIFT CITY, Block 53, Zone 5
Verify the current registration details
NiveshCheck records the SEBI registration number above from publicly available information. Registration status can change, so check the current record directly in SEBI's registered stock-broker directory before opening an account or making a decision.
Search INZ000200531 on SEBI →Use this record responsibly
This profile is a record of published information, not an assessment of this broker. Use the official SEBI directory for the current record and read our neutral guide before relying on a registration number or broker name.
Recorded equity exchange memberships
These memberships are recorded from NiveshCheck's documented SEBI equity-source material. They do not establish membership in other market segments.
Frequently asked questions
What is Navkar Share & Stock Brokers Private Limited.'s recorded SEBI registration number?
Navkar Share & Stock Brokers Private Limited.'s recorded SEBI registration number on NiveshCheck is INZ000200531. Check the current record directly with SEBI before relying on it.
How can I check Navkar Share & Stock Brokers Private Limited.'s current SEBI record?
Use the official SEBI registered stock-broker directory and search for INZ000200531. The official record may change after NiveshCheck's review date.
Does NiveshCheck recommend Navkar Share & Stock Brokers Private Limited.?
No. NiveshCheck is an independent directory and does not recommend, endorse, certify, or assess the suitability of brokers.
See a factual error? Suggest a correction or read our methodology.