Company Disclosure

Rasandik Engineering Industries India Limited (Scrip Code: 522207) has submitted an intimation to BSE under Regulation 30 read with Schedule III of SEBI (Listing Obligations and Disclosure Requirements) Regulations, 2015 regarding communication with shareholders.

Key Dates

  • Letter Date: July 6, 2026 (shareholder communication date)
  • Cut-off Date: July 3, 2026 (for determining non-registered email shareholders)
  • AGM Date: July 31, 2026 at 11:00 AM IST
  • SEBI Circular Effective Date: April 1, 2024 (for electronic payment mandate)

AGM Details

The 42nd Annual General Meeting of Rasandik Engineering Industries India Limited will be held on July 31, 2026 at 11:00 AM IST through Video Conferencing (VC) facility / Other Audio Visual Means (OAVM).

Document Access

Shareholders without registered email addresses can access the Annual Report for Financial Year 2025-2026 and the AGM notice at the company's website: www.rasandik.com/report.html

Regulatory Compliance Requirements

The company reminds shareholders of SEBI Master Circular No. SEBI/HO/MIRSD/POD-1/P/CIR/2024/37 dated May 7, 2024, which mandates:

  • PAN registration
  • Address with PIN code
  • Mobile number
  • Bank account details
  • Specimen signature
  • Choice of nomination

for all physical security holders. Email registration is optional but recommended.

Payment Restrictions

Physical security holders without updated KYC details will only receive payments (dividend, interest, redemption) through electronic mode effective April 1, 2024.

Service Channels

Shareholder queries and service requests should be directed to:

KYC Documentation

Required forms (ISR-1, ISR-2, ISR-3, SH-13, SH-14) and SEBI circulars are available on the RTA's website under Resources > Downloads > KYC > Formats for KYC.

Green Initiative

Shareholders are encouraged to update email addresses to receive electronic communications and support environmental initiatives.

#Tags: #RasandikEngineering #AGM2026 #SEBIDisclosure #RegulatoryCompliance #ShareholderCommunication