Avana Electrosystems IPO Allotment Status: Check Online & Direct Links
Check your Avana Electrosystems allotment status online using PAN, Application Number, or Demat Account. This step-by-step guide will help you verify if you received shares in the Avana Electrosystems IPO.
How to Check Avana Electrosystems IPO Allotment Status
There are three main methods to check your Avana Electrosystems IPO allotment status. Choose the one that's most convenient for you:
Check via Registrar Portal (Integrated Registry Management Services Pvt.Ltd.)
Fastest and most reliable method
- 1
Visit the Official Registrar Website
https://www.bseindia.com/investors/appli_check.aspx - 2
Select "Avana Electrosystems IPO" from the IPO dropdown menu
- 3
Choose search type: PAN, Application Number, or Demat Account
- 4
Enter your details and click Submit
- 5
View your allotment status - shows number of shares allotted (if any)
Check via BSE Website
Official stock exchange portal
- 1
Visit BSE IPO Status Page
www.bseindia.com/investors/appli_check.aspx - 2
Select issue type: Equity
- 3
Select "Avana Electrosystems IPO" from the issue name dropdown
- 4
Enter your Application Number and PAN
- 5
Click Search to view your status
Check via NSE Website
National Stock Exchange portal
- 1
Visit NSE IPO Status Page
www.nseindia.com - 2
Enter your PAN or Application Number
- 3
Complete the captcha verification
- 4
Click Submit to view allotment details
Avana Electrosystems IPO Important Dates
IPO Open Date
Mon, Jan 12, 2026
IPO Close Date
Wed, Jan 14, 2026
Allotment Date
Thu, Jan 15, 2026
Refund Initiation
Fri, Jan 16, 2026
Credit to Demat
Fri, Jan 16, 2026
Listing Date
Tue, Jan 20, 2026
Important Tips for Checking Allotment
Check allotment status after 6 PM on the allotment date for best results
Keep your PAN number and Application number handy
If not allotted, your money will be refunded automatically within 1-2 working days
Allotted shares will be credited to your demat account on the credit date
If you don't see your status, wait a few hours and try again - servers may be busy